Updating

Updating Atrium means pulling a newer version of the Docker image and restarting the container. Database migrations run automatically on startup — you do not need to run them manually.

Check the changelog before updating. Breaking changes, new required environment variables, or other migration notes are listed there.

Your data is stored in Docker volumes, not inside the image. Pulling a new image and restarting the container does not delete your database or uploaded files.

Docker

Pull the latest image

docker pull vibralabs/atrium:latest

Restart the container

docker stop atrium
docker rm atrium
docker run -d \
  --name atrium \
  -p 8080:8080 \
  -v atrium-db:/var/lib/postgresql/data \
  -v atrium-uploads:/app/uploads \
  -e BETTER_AUTH_SECRET=your-secret-here \
  vibralabs/atrium:latest

Use the same docker run flags you used when you first installed Atrium.

Docker Compose

docker compose pull && docker compose up -d

This pulls the latest image for every service in your docker-compose.yml and recreates any containers that have a newer image available.

Unraid

In the Unraid Docker UI, click the container icon and select Force Update.

Restarting the container in Unraid does not pull a newer image. You must use Force Update to fetch the latest version from Docker Hub.

What happens on startup

When the container starts after an update, Atrium automatically applies any database schema changes. This is safe to run repeatedly — only new changes are applied. If your database connection goes through a pooler like PgBouncer, set SKIP_DB_PUSH=true to skip the automatic schema sync. You’ll need to provide a DIRECT_URL for a non-pooled connection instead. See Docker for details.

Deployment

Operations

Docker

Docker Compose

Unraid

What happens on startup

​Docker

​Docker Compose

​Unraid

​What happens on startup

Docker

Docker Compose

Unraid

What happens on startup