RackPeek can run in two ways:
RackPeek stores everything in a writable config/ directory as YAML (including automatic backups).
Wherever you run it, that directory must be writable.
Saves are atomic: the config is written to a temporary file, flushed to disk, then renamed
over config.yaml. An interrupted save therefore leaves the previous config intact rather
than a half-written one. If the config ever does become unreadable — a damaged disk, a bad
hand edit, a sync conflict — RackPeek refuses to read or write it rather than reporting an
empty inventory, and the Web UI's YAML editor (/yaml) still loads so you can repair it.
This gives you:
8080version: "3.9"
services:
rackpeek:
image: aptacode/rackpeek:latest
container_name: rackpeek
ports:
- "8080:8080"
volumes:
- rackpeek-config:/app/config
restart: unless-stopped
healthcheck:
test: ["CMD", "curl", "-fsS", "http://localhost:8080/health"]
interval: 30s
timeout: 5s
start_period: 15s
retries: 3
volumes:
rackpeek-config:
Start it:
docker compose up -d
Open:
http://localhost:8080
This uses a named volume, which avoids permission issues and is recommended for most users.
RackPeek stores its ASP.NET DataProtection keys under config/.dataprotection on the same volume, so browser sessions survive container upgrades. If you run the container with a read-only root filesystem, also mount a tmpfs for the app's temp directory:
read_only: true
tmpfs:
- /app/tmp:uid=1654,gid=0
Use the same Compose file above in a stack. Portainer typically handles user permissions automatically.
If you want the YAML stored directly on your host:
volumes:
- /path/on/host/rackpeek:/app/config
⚠️ The directory must be writable.
If you see:
Access to the path '/app/config/config.yaml' is denied.
Fix ownership — RackPeek runs as UID/GID 1654:1654 inside the container:
sudo chown -R 1654:1654 /path/on/host/rackpeek
You can verify the container user with:
docker exec rackpeek id
RackPeek must be able to:
config.yamlPermission issues are almost always the cause of startup failures.
If running Docker, you already have the CLI.
Run commands directly inside the container:
docker exec -it rackpeek rpk --help
docker exec -it rackpeek rpk systems list
If you prefer running RackPeek directly on Linux:
wget https://github.com/Timmoth/RackPeek/releases/download/RackPeek-2.3.0/rackpeek_2_3_0_linux-x64 -O rackpeek
Or:
curl -L https://github.com/Timmoth/RackPeek/releases/download/RackPeek-2.3.0/rackpeek_2_3_0_linux-x64 -o rackpeek
chmod +x rackpeek
sudo mv rackpeek /usr/local/bin/rpk
RackPeek expects a config folder next to the binary:
sudo mkdir -p /usr/local/bin/config
sudo touch /usr/local/bin/config/config.yaml
⚠️ It must be writable, since RackPeek writes backups there as well.
If needed:
sudo chown -R $USER:$USER /usr/local/bin/config
rpk --help
RackPeek stores everything in plain YAML:
config/
└── config.yaml
No database. No telemetry. No lock-in.
You own your data.