Upgrade Remote Worker container with containerized add-ons


A Linux host with a previous containerized version of pliant worker already installed

Download the container images package: https://distributor.pliant.io/pliant-worker-airgap.tar.gz

Expand the tarball and load the images into docker:

tar -xvf ./pliant-worker-airgap.tar.gz
sudo docker load -i ./pliant-worker/pliant-worker-images.tar

If using podman instead of docker, issue the following command instead:

sudo podman  load -i ./pliant-worker/pliant-worker-images.tar

Backup the ./worker-config.env file. It should not be overwritten, but backups are always recommended when performing a change.

If necessary, copy the worker-config.env file into place and bring up the remote worker

sudo docker-compose -f ./pliant-worker/docker-compose.yml -p pliant-worker up -d

The worker should now be running along with all currently available integration addons.

CentOS Stream 9

docker-compose is not installed by default on CentOS9 with podman. Follow these instructions to install docker-compose and start the pliant-worker:

sudo curl -L https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m) -o /usr/local/bin/docker-compose
sudo chmod 755 /usr/local/bin/docker-compose
sudo systemctl enable podman.socket
sudo systemctl start podman.socket
sudo /usr/local/bin/docker-compose -f ./pliant-worker/docker-compose.yml  -p pliant-worker up -d


To stop the worker and all addon containers, we would issue:

sudo docker-compose -f ./pliant-worker/docker-compose.yml -p pliant-worker down

Note: Restarting the worker container will not make any configuration changes take effect. You must use the docker-compose commands to stop and start the containers if any changes are needed.

Troubleshooting Commands

See worker log output:

sudo docker container logs $(docker ps |grep pliant-worker_pliant-worker | awk '{print $1}')