How to Update Dockge to the Latest Version

Published 2026-06-08Updated 30 Aug 20263 min readdockge.org editorial desk
Terminal showing the Dockge update commands with a refresh icon

Updating Dockge takes two commands and never touches your stacks, because every stack is just a file in /opt/stacks. Here is the safe upgrade routine, plus how to verify the version and roll back if needed.

The standard update procedure

cd /opt/dockge
docker compose pull
docker compose up -d

pull downloads the newest image; up -d recreates the container on it. The whole process usually finishes in under a minute, and running stacks keep running throughout.

What survives an update

  • Your stacks — untouched, they live outside the Dockge container.
  • Your login and settings — stored in the mounted data volume.
  • Running containers — only the Dockge container itself restarts.

Check which version you are running

The version is shown at the bottom of the Dockge interface. From the shell you can also inspect the image tag:

docker inspect dockge --format '{{.Config.Image}}'

Rolling back to a previous version

If a release misbehaves, pin the previous tag in /opt/dockge/compose.yaml:

services:
  dockge:
    image: louislam/dockge:1.4

Then run docker compose up -d again. Return the tag to :1 or :latest when you want to move forward.

Update problems?

A failed pull is usually a network or disk-space issue — run docker system df to check space. If the interface won't load after updating, clear the browser cache and see the common errors guide. Keeping Dockge current is also the best security habit alongside a strong admin login.

Back up Dockge's own data before major changes

Your managed Compose stacks live in the configured stacks directory, while Dockge's application data is normally mounted from ./data in the Dockge installation directory. Before a major maintenance change, copy the Compose file and application-data directory so account and configuration data can be restored if needed.

cd /opt/dockge
cp compose.yaml compose.yaml.backup
cp -a data data.backup

Verify after the update

docker compose ps
docker compose logs --tail=100 dockge
docker image ls louislam/dockge

Confirm that the service is running and that the UI loads normally before deleting any backup. If you use the optional Console, remember that Dockge 1.5.0 disables it by default for security.

Do not update Dockge from an untrusted image

The official Compose definition uses the louislam/dockge image. Avoid third-party images that claim to be modified or preconfigured Dockge builds unless you have independently audited them.

Your stacks are separate from Dockge's application data

Updating the Dockge container should not rewrite Compose stacks stored in your configured stacks directory. That separation is one of Dockge's core design choices. It is still wise to back up important stack files, environment files and persistent application data as part of normal server maintenance; a container-manager update is not a substitute for backups.

Before updating a production host, read the latest upstream release notes for breaking changes and security notes rather than assuming every release behaves identically.

Official references

Technical details in this guide are checked against upstream sources. Verify release-sensitive commands before changing a production host.

Related guides