59cb3a4fbc
The group_add fix itself already landed on master (ddae57c) but the running
container still has GroupAdd=[999] — deploy pending from main checkout.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
20 lines
846 B
YAML
20 lines
846 B
YAML
services:
|
|
node-agent:
|
|
# Docker GID on SOLARIA is 996 (not the Debian default 999 the base compose
|
|
# assumes). Without this the agent starts with "Docker unavailable:
|
|
# Permission denied" on /var/run/docker.sock and reports no containers
|
|
# (recon RECON-multiagent-2026-07-27.md, A2/E19). Compose concatenates
|
|
# group_add lists, so the base 999 stays alongside; 996 is what grants
|
|
# socket access here. Same per-host pattern as piha (123) and lustro (991).
|
|
group_add:
|
|
- "996" # host docker gid, verified 2026-07-30 (getent group docker → 996)
|
|
environment:
|
|
- NODE_NAME=solaria
|
|
- NODE_TYPE=ai_node
|
|
- VPS_EVENTS_HOST=100.95.58.48
|
|
- VPS_EVENTS_USER=oskar
|
|
- VPS_EVENTS_PATH=/opt/homelab/events
|
|
- CHECK_INTERVAL=60
|
|
volumes:
|
|
- /home/oskar/.ssh:/home/homelab/.ssh:ro
|