Updating the IBM Db2 Warehouse client container (Linux)

To update your Db2® Warehouse client container, download a new container.

Before you begin

Ensure that your Linux® system meets the prerequisites described in Getting container images.

See the information about the container location in Deploying the IBM Db2 Warehouse client container (Linux).

About this task

To perform this task, you must have root authority on the host operating system.

Procedure

Log in to Docker or Podman using your API key:
```
echo <apikey> | docker login -u iamapikey --password-stdin icr.io
```
```
echo <apikey> | podman login -u iamapikey --password-stdin icr.io
```
where <apikey> is the API key that you created as a prerequisite in Getting container images.

To reduce system downtime, issue one of the following Docker or Podman commands:

For a container for POWER® LE hardware:

docker pull icr.io/obs/hdm/db2wh_ce:v11.5.7.0-cn5-db2wh_client-ppcle

podman pull icr.io/obs/hdm/db2wh_ce:v11.5.7.0-cn5-db2wh_client-ppcle

For a container for x86 hardware:

docker pull icr.io/obs/hdm/db2wh_ce:v11.5.7.0-cn5-db2wh_client-linux

podman pull icr.io/obs/hdm/db2wh_ce:v11.5.7.0-cn5-db2wh_client-linux

Stop the client container by issuing the following Docker or Podman command:
```
docker stop client
```
```
podman stop client
```
Perform one of the following steps:
- Remove the old container by issuing the following Docker or Podman command:
```
docker rm -f client
```
```
podman rm -f client
```
- Rename the old container, for example:
```
docker rename client client-old
```
  Note: The rename command is not supported with Podman.

Issue the applicable docker run or podman run command:

Note: The /mnt/tools path shown here is only an example. Replace it with the path that was specified for the docker run or podman run command during deployment.

For POWER LE hardware:

docker run -dit --net=host -v /mnt/tools:/mnt/clientdir [-v /mnt/clusterfs/home/db2inst1:/mnt/blumeta0/home/db2inst1] --name=client icr.io/obs/hdm/db2wh_ce:v11.5.7.0-cn5-db2wh_client-ppcle

podman run -dit --net=host -v /mnt/tools:/mnt/clientdir [-v /mnt/clusterfs/home/db2inst1:/mnt/blumeta0/home/db2inst1] --name=client icr.io/obs/hdm/db2wh_ce:v11.5.7.0-cn5-db2wh_client-ppcle

For x86 hardware:

docker run -dit --net=host -v /mnt/tools:/mnt/clientdir [-v /mnt/clusterfs/home/db2inst1:/mnt/blumeta0/home/db2inst1] --name=client icr.io/obs/hdm/db2wh_ce:v11.5.7.0-cn5-db2wh_client-linux

podman run -dit --net=host -v /mnt/tools:/mnt/clientdir [-v /mnt/clusterfs/home/db2inst1:/mnt/blumeta0/home/db2inst1] --name=client icr.io/obs/hdm/db2wh_ce:v11.5.7.0-cn5-db2wh_client-linux

Specify the -v /mnt/clusterfs/home/db2inst1:/mnt/blumeta0/home/db2inst1 parameter only if you are planning to load locally, that is, to issue the dbload command from the client container to load from the host machine on which the Db2 Warehouse database is located. For information about loading locally, see dbload command.

Review the log output to verify that the update is progressing successfully. Issue the following Docker or Podman command:
```
docker logs --follow client
```
```
podman logs --follow client
```
Exit the logs by pressing Ctrl+C.

What to do next

As part of the update process, the .bashrc and .bash_profile files are backed up as bashrc.bak and bash_profile.bak files and then overwritten. If you customized the .bashrc or .bash_profile file before the container update, reapply those customizations from the applicable backup file.

If you no longer require the container, stop it and remove it by issuing the following Docekr or Podman commands:

docker stop client
docker rm client

podman stop client
podman rm client