Rackula
Stack
Plan your rack layout. Drag your devices in, move them around, export it. It runs in your browser. You can close the tab whenever you want
Services
rackula
Configuration
Imageghcr.io/rackulalives/rackula:latest8383:8080API_HOST=rackula-apiAPI_PORT=3001RACKULA_LISTEN_PORT=8080API_WRITE_TOKEN=${RACKULA_API_WRITE_TOKEN:-}RACKULA_AUTH_MODE=${RACKULA_AUTH_MODE:-none}RACKULA_ENABLE_IPV6=${RACKULA_ENABLE_IPV6:-auto}NGINX_RESOLVER=127.0.0.11alwaysImage details
rackula-api
Configuration
Imageghcr.io/rackulalives/rackula-api:latest/data : /portainer/Files/AppData/Config/rackula/dataDATA_DIR=/dataRACKULA_API_PORT=3001CORS_ORIGIN=${CORS_ORIGIN:-http://localhost:8383}RACKULA_API_WRITE_TOKEN=${RACKULA_API_WRITE_TOKEN:-}RACKULA_AUTH_MODE=${RACKULA_AUTH_MODE:-none}RACKULA_AUTH_SESSION_SECRET=${RACKULA_AUTH_SESSION_SECRET:-}RACKULA_AUTH_SESSION_MAX_AGE_SECONDS=${RACKULA_AUTH_SESSION_MAX_AGE_SECONDS:-43200}RACKULA_AUTH_SESSION_IDLE_TIMEOUT_SECONDS=${RACKULA_AUTH_SESSION_IDLE_TIMEOUT_SECONDS:-1800}RACKULA_AUTH_SESSION_GENERATION=${RACKULA_AUTH_SESSION_GENERATION:-0}RACKULA_AUTH_SESSION_COOKIE_SAMESITE=${RACKULA_AUTH_SESSION_COOKIE_SAMESITE:-Lax}RACKULA_AUTH_SESSION_COOKIE_SECURE=${RACKULA_AUTH_SESSION_COOKIE_SECURE:-true}RACKULA_AUTH_CSRF_PROTECTION=${RACKULA_AUTH_CSRF_PROTECTION:-true}ALLOW_INSECURE_CORS=${ALLOW_INSECURE_CORS:-false}alwaysImage details
Standalone Install
Select an install method, to see config/commands for deploying Rackula
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Rackula, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Original stackfile
The compose file this template deploys, straight from its repo:
services:
rackula:
image: ghcr.io/rackulalives/rackula:latest
container_name: rackula
restart: always
ports:
- "8383:8080"
environment:
- API_HOST=rackula-api
- API_PORT=3001
- RACKULA_LISTEN_PORT=8080
- API_WRITE_TOKEN=${RACKULA_API_WRITE_TOKEN:-}
- RACKULA_AUTH_MODE=${RACKULA_AUTH_MODE:-none}
- RACKULA_ENABLE_IPV6=${RACKULA_ENABLE_IPV6:-auto}
- NGINX_RESOLVER=127.0.0.11
stop_grace_period: 10s
deploy:
resources:
limits:
cpus: "0.50"
memory: 128M
reservations:
cpus: "0.10"
memory: 16M
#security_opt:
# - no-new-privileges:true
#cap_drop:
# - ALL
#read_only: true
tmpfs:
- /var/cache/nginx:size=10M
- /var/run:size=1M
- /tmp:size=5M
- /etc/nginx/conf.d:size=1M,uid=101,gid=101
logging:
driver: json-file
options:
max-size: "10m"
max-file: "3"
depends_on:
- rackula-api
rackula-api:
image: ghcr.io/rackulalives/rackula-api:latest
container_name: rackula-api
restart: always
stop_grace_period: 10s
volumes:
# Host directory must be writable by container user (uid 1001)
# Run: mkdir -p /portainer/Files/AppData/Config/rackula/data && chown 1001:1001 /portainer/Files/AppData/Config/rackula/data
- /portainer/Files/AppData/Config/rackula/data:/data
environment:
- DATA_DIR=/data
- RACKULA_API_PORT=3001
- CORS_ORIGIN=${CORS_ORIGIN:-http://localhost:8383}
- RACKULA_API_WRITE_TOKEN=${RACKULA_API_WRITE_TOKEN:-}
- RACKULA_AUTH_MODE=${RACKULA_AUTH_MODE:-none}
- RACKULA_AUTH_SESSION_SECRET=${RACKULA_AUTH_SESSION_SECRET:-}
- RACKULA_AUTH_SESSION_MAX_AGE_SECONDS=${RACKULA_AUTH_SESSION_MAX_AGE_SECONDS:-43200}
- RACKULA_AUTH_SESSION_IDLE_TIMEOUT_SECONDS=${RACKULA_AUTH_SESSION_IDLE_TIMEOUT_SECONDS:-1800}
- RACKULA_AUTH_SESSION_GENERATION=${RACKULA_AUTH_SESSION_GENERATION:-0}
- RACKULA_AUTH_SESSION_COOKIE_SAMESITE=${RACKULA_AUTH_SESSION_COOKIE_SAMESITE:-Lax}
- RACKULA_AUTH_SESSION_COOKIE_SECURE=${RACKULA_AUTH_SESSION_COOKIE_SECURE:-true}
- RACKULA_AUTH_CSRF_PROTECTION=${RACKULA_AUTH_CSRF_PROTECTION:-true}
- ALLOW_INSECURE_CORS=${ALLOW_INSECURE_CORS:-false}
deploy:
resources:
limits:
cpus: "0.25"
memory: 64M
reservations:
cpus: "0.05"
memory: 16M
security_opt:
- no-new-privileges:true
cap_drop:
- ALL
read_only: true
tmpfs:
- /tmp:size=5M
healthcheck:
test: ["CMD", "wget", "-qO-", "http://127.0.0.1:3001/health"]
interval: 30s
timeout: 10s
start_period: 5s
retries: 3
logging:
driver: json-file
options:
max-size: "5m"
max-file: "2"
expose:
- "3001"
Or deploy it directly from the source:
git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/rackula.yml up -dMore install options in our documentation.
Serve Rackula on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying rackula.example.com to http://rackula:8080
Add this to your Caddyfile
rackula.example.com {
reverse_proxy http://rackula:8080
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:8383 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :8383 - Stop the other service, or pick a different host port. In
8383:8080only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:8383. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, rackula can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8383
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /portainer/Files/AppData/Config/rackula/data
Image won't pull
Test the pull directly on the host: docker pull ghcr.io/rackulalives/rackula:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The always restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect <container> --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Stack won't deploy
Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.
- YAML only accepts spaces for indentation, a single tab breaks the whole file.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within rackula's repo
- Template not working: Open an issue on xneo1/portainer_templates
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Rackula is a Compose stack, a set of containers (2 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.
The services
This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:
rackularunsghcr.io/rackulalives/rackula:latest, starts after rackula-apirackula-apirunsghcr.io/rackulalives/rackula-api:latest
Ports
A port is the door the app answers on. A mapping like 8383:8080 means it's reachable on port 8383 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8383 in a browser. It opens:
8383:8080, likely the web interface
Volumes
A volume is where Rackula keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/datafrom/portainer/Files/AppData/Config/rackula/dataon the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Rackula takes 19 of them, all with defaults you can leave alone or tweak:
API_HOST, defaults torackula-apiAPI_PORT, defaults to3001RACKULA_LISTEN_PORT, defaults to8080API_WRITE_TOKEN, pulled from your own environmentRACKULA_AUTH_MODE, defaults tononeRACKULA_ENABLE_IPV6, defaults toautoNGINX_RESOLVER, defaults to127.0.0.11DATA_DIR, defaults to/dataRACKULA_API_PORT, defaults to3001CORS_ORIGIN, defaults tohttp://localhost:8383RACKULA_API_WRITE_TOKEN, pulled from your own environmentRACKULA_AUTH_SESSION_SECRET, pulled from your own environmentRACKULA_AUTH_SESSION_MAX_AGE_SECONDS, defaults to43200RACKULA_AUTH_SESSION_IDLE_TIMEOUT_SECONDS, defaults to1800RACKULA_AUTH_SESSION_GENERATION, defaults to0RACKULA_AUTH_SESSION_COOKIE_SAMESITE, defaults toLaxRACKULA_AUTH_SESSION_COOKIE_SECURE, defaults totrueRACKULA_AUTH_CSRF_PROTECTION, defaults totrueALLOW_INSECURE_CORS, defaults tofalse
Restart policy
The restart policy here is always, so Docker brings Rackula back up after a crash and again when the server reboots. Good for anything you want running around the clock. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Portainer puts these services on one shared private network, so they can find each other by name (like rackula) while only the ports above are open to you.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Rackula up. Add the template list to Portainer once, then deploying Rackula is a click rather than a wall of config.