Prerequisites
- Unraid 6.x or 7.x
- Docker enabled in Unraid settings
Install via Community Applications
An official Community Applications template is available. Search for Atrium in the Apps tab and click Install. The template pre-fills the repository, port mapping, and volume paths described below.Manual installation
If you prefer to set up the container yourself:1
Open the Docker UI
In the Unraid web UI, go to the Docker tab and click Add Container.
2
Set the repository
Set Repository to:Set Network Type to
Bridge.3
Map the port
Add a port mapping:
4
Add environment variables
Add the following environment variables. In the Unraid UI, make sure both the Name/Key field and the Value field are filled in for each variable — if the Key field is empty, Unraid silently drops the variable and the container will fail to start.
5
Map the volumes
Add the following path mappings:
6
Apply and open
Click Apply. Once the container starts, open
http://your-unraid-ip:8080 (or your chosen host port) and create your account.Why SECURE_COOKIES=false?
By default, Atrium sets cookies with theSecure flag, which instructs browsers to only send them over HTTPS connections. When you access Atrium over plain HTTP (typical for local-network Unraid setups), the browser silently drops these cookies and every request returns a 403 Invalid or missing CSRF token error.
Setting SECURE_COOKIES=false removes the Secure flag so cookies work over plain HTTP.
Optional configuration
External database
External database
To use an existing PostgreSQL instance instead of the built-in one, add these variables:
You can remove the
/var/lib/postgresql/data volume mapping when using an external database.Email notifications
Email notifications
To enable email notifications (invitations, password resets):
S3 file storage
S3 file storage
To use S3-compatible storage instead of local disk:
You can remove the
/app/uploads volume mapping when using S3 storage.Updating
In the Unraid Docker UI, click the container icon and select Force Update.Simply restarting the container does not pull a newer image. You must use Force Update to fetch the latest version from Docker Hub. Database migrations run automatically when the container starts.