Updating Existing Containers

When new software in the form of a Docker image is released, containers need to be individually updated to run the latest version as they do not automatically run the latest image. In this example, the Intercom is used. The same process applies to Beacon, Intercom Dashboard, and any other future images.

Assuming the system hasn't already been updated, it will look similar to Figure 6 below before starting. The Image section contains the following images:

• Portainer

• Beacon

• Intercom

• Intercom Dashboard

All are using the :latest tag.

Figure 6 - Updating the existing container

Assuming the registry is correctly set in the Registries tab, change the following:

• Registry: Quay

• Image: <beacon:latest | intercom:latest | intercom-dashboard:latest>

You may specify a specific version (such as intercom: 2.1.10), however, we recommend using the :latest tag.

Figure 7 - Pulling the latest image

Once the image has successfully been pulled, the list will look like Figure 8 below:

Figure 8 - The list after pulling the image

Note how the tag has changed:

• sha256:640679[...] quay.io/telosalliance/intercom:latest

  • The “latest” intercom image that was just pulled.

  • It currently shows “Unused” because it is not yet active in any container.

• sha256:0d8aeb[...] quay.io/telosalliance/intercom:<none>

  • The previous "latest" image.

  • There can only be one image with the tag :latest, so every time a new “latest” image is pulled, the old “latest” will still remain but have its tag removed and set to .

  • It is accessible now only by sha256 or a user-defined tag.

Important - Unless the ":<none>" image also shows "Unused," do not remove it, as it is still in use by one or more containers.

Update the containers by navigating to Containers > Name, then clicking the "Recreate" button.

Figure 9 - Recreating the container

Click on "Recreate" again. It is not necessary to enable "Pull latest image" as the latest image is already present.

Figure 10 - Verifying recreating the container

The vip1 container has now been updated to use the intercom:latest image, and you can see which containers are using the :latest image and which are not.

In Figure 11 below, vip1 is using intercom:latest.

vip2 is using image sha256:0d8aeb[...] quay.io/telosalliance/intercom:<none>. This is the previous intercom:latest which has had its tag removed and replaced with :<none>.

Figure 11 - Viewing which images are currently in use