menzeljandClaude Opus 5
6af02a1367
The shipped default (./data/stacks) guarantees the mismatch that hid stack data from the file browser, the editor and (before 0.40.0) from backups: compose resolves ./config against the container path, so the daemon creates the data directories at /opt/stacks/<stack>/... on the host regardless of where STACKS_HOST_DIR points. Same change for the agent, plus the reasoning in .env.example and the README config table. Images unchanged (0.40.1). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
27 lines
1.1 KiB
YAML
27 lines
1.1 KiB
YAML
# StackPilot agent — deploy this on each remote host you want to manage.
|
|
# It needs only the Docker socket and a shared AGENT_TOKEN (must match the
|
|
# token you enter when adding this host in the central StackPilot UI).
|
|
services:
|
|
agent:
|
|
image: 10.10.6.10:3020/menzelj/stackpilot-agent:latest
|
|
build:
|
|
context: .
|
|
args:
|
|
BACKEND_IMAGE: 10.10.6.10:3020/menzelj/stackpilot-backend:latest
|
|
restart: unless-stopped
|
|
environment:
|
|
- AGENT_TOKEN=${AGENT_TOKEN:?set AGENT_TOKEN in .env}
|
|
- STACKS_DIR=/opt/stacks
|
|
- HOST_PROC_PATH=/host_proc
|
|
volumes:
|
|
- /var/run/docker.sock:/var/run/docker.sock
|
|
# Same rule as the central app: this must resolve to the same path as
|
|
# STACKS_DIR, or the stacks' relative bind mounts (./config) end up at the
|
|
# container path on the host, where the agent cannot see them.
|
|
- ${STACKS_HOST_DIR:-/opt/stacks}:/opt/stacks
|
|
- /proc:/host_proc:ro
|
|
# Read-only host devices for status/detection parity with the main host.
|
|
- /dev:/dev:ro
|
|
ports:
|
|
- "5010:5010"
|