Update your installation

Review the release notes and back up your data before updating.

Docker Compose

Return to the omnimatch folder you created during setup, which contains compose.yaml. Pull the latest approved image and recreate the container:

docker compose pull    # Download the latest image
docker compose up -d   # Start in the background
docker compose logs -f # Follow startup logs

Press Ctrl+C to stop following the logs. Omnimatch keeps running in the background.

For a controlled release, replace onprem-stable in your Compose file with the immutable tag or digest supplied for that release.

Kubernetes

Set the Deployment’s image to the new immutable tag or digest, then apply the manifest and check the rollout:

kubectl -n omnimatch apply -f kubernetes.yaml
kubectl -n omnimatch rollout status deployment/omnimatch

Keep one replica and the Recreate strategy. Preserve the existing persistent volume claim. Reapplying an unchanged onprem-stable tag does not trigger an update; use the release’s immutable reference.

Air-gapped installations

Transfer the new image archive to your isolated server, then load it before recreating the container:

docker load -i omnimatch.tar
docker compose up -d --pull never --force-recreate
docker compose logs -f # Follow startup logs

Preserve your data

Your data stays in the volume. Never delete it with docker compose down -v unless you intend to remove your data.