Update Containly

Your data stays in the named volumes (containly-data, containly-stacks) and your Compose folders, so an update only replaces the container.

See whether an update is there

Containly checks for new versions on its own (every 6 hours) and shows them on the Updates page; "Check now" checks right away. From Containly 2.5.0 only a strictly newer release counts as an update, so a development build or a newer build than the latest release is never offered an older version. The Version and licence tab in the settings shows the release notes of the latest version.

Update in the app

On the Updates page, update the Containly image like any other. Containly recreates its own container on the new version and rolls back to the previous one if the new version does not start up healthy. When "Update all" includes Containly itself, that update runs last and the page reloads afterwards.

Update with Docker Compose

In the folder with your docker-compose.yml:

docker compose pull
docker compose up -d

This also updates Containly, but without the automatic rollback.

Update a docker run installation

Pull the new image, remove the old container and start it again with the same command you used to install (the volumes keep your data):

docker pull amslertec/containly:latest
docker stop containly
docker rm containly

Then run your docker run command from the install guide again.

After the update

• Reload the browser tab. If you installed Containly as an app (PWA), close and reopen it.
• A Pro licence stays active: it is stored in the data volume and does not need a new activation.
• From Containly 2.1.0 on, keys from the Containly shop (they start with CL1-) are accepted. An older version does not accept them: update first.