Read this post to learn more how to update a container in TripleO on a live system.

Note: this might sound surgery but this is I think the clean options to patch container images in TripleO.

Your TripleO cloud is running and you want to update an rpm in one or multiple containers?

TripleO provides some CLI to build new container images with the rpms that you want. This procedure is also documented here.

In this particular example, we will update the python3-networking-ovn rpm on octavia_api.

  1. You need a host to build the image:

The easiest place is the Undercloud or the Standalone node, where Buildah and tripleoclient are installed. We’ll build the image from that host.

  1. Put your rpms in a directory:

e.g. in /tmp/rpms

  1. Export the OpenStack admin credentials: e.g.:
export OS_CLOUD=standalone
  1. Login to the registry (when using OSP):
podman login
  1. Build the new container image for octavia_api:
openstack tripleo container image hotfix \
    --image \
    --rpms-path /tmp/hotfix \
    --tag 16.2-customfix \

You should see the new image by running buildah images.

Now you’ll need to push the image to a registry (yours, or TripleO registry): e.g. :

buildah push docker://

Now, there are two methods for deploying that new image.

  • Run the deploy command again, after updating the ContainerOctaviaApiImage parameter in TripleO environment
  • Run the following steps:

You need to figure out what’s the TripleO step where Octavia is deployed (it’s step 4), by looking on the host in /var/lib/tripleo-config/container-startup-config and grep for octavia_api.

Now, go on the host where you want to use that new image (in the case of Standalone, it’s the same host where you built the image) and create an Ansible playbook with this content (e.g. paunch.yaml):

- hosts: localhost
  become: true
    service_name: octavia_api
  - name: Stop and clean the old container
    command: systemctl stop {{ service name }} && podman rm {{ service_name }}
  - name: Start containers for step 1
      config: /var/lib/tripleo-config/container-startup-config/step_4/hashed-{{ service_name }}.json
      config_id: tripleo_step4
      cleanup: false
      action: apply

Change the content for your needs (different step, image, etc).

Run Ansible with:

ansible-playbook paunch.yaml

Your container is now running with your custom image (check with podman inspect).

For more details or help, check out the TripleO manuals or ask for help on IRC #tripleo (OFTC now).