Upgrading to a Patch Build in Docker

When an FME Server build is released, three tags are created for each component’s image. For example, if the released build is 20238, these tags are named 20238, 20238-latest, and 20238-20200511, where 20200511 is the date the image was released.

The available tags for each FME Server component can be found on Dockerhub or Quay.io. From within any of the repositories under the safesoftware organization (fmeserver-core, fmeserver-engine,...), search for a build number (for example, 20238) to find all of the tags for that build.

Patch Builds

Images of each build are patched periodically with security updates. When this occurs, each image is released again with the current date as a suffix to the build number (for example, 20238-20200523), and the other tags (for example, 20238 and 20238-latest) are updated to refer to the most recently released version of the build. With this in mind, if it is preferable to lock down to a specific image and avoid updating to a patched version, use the timestamped tags. Otherwise, to always use the latest version of a build, use the non-timestamped tag (for example, 20238 or 20238-latest).

To upgrade to the latest patch build in a Docker Compose deployment

  1. Pull the latest images. Run:

    2. >> docker-compose pull

  2. Update the FME Server deployment with the new images. Run:

    3. >> docker-compose -f docker-compose.yml up -d

  3. Remove the old images. (They should be listed with repository <none> and tag <none>.)

To upgrade to a specific patch build

  1. Search for the build on Dockerhub or Quay.io, which will display each of the patch builds for that build number.
  2. In your docker compose file, update each image tag (after the ‘:’ in the image name) to the desired build/timestamp.
  3. Update the FME Server deployment with the new images. Run:

    4. >> docker-compose -f docker-compose.yml up -d

See Also