Root cause of the long-standing cloud_provider: steel residue: the 2026-07-30 rollback disabled the browser-steel plugin and set browser.engine: camofox but left browser.cloud_provider: steel in config.yaml. The split config was inert-but-wrong, so it survived ~3 months of audits unnoticed. Corrects pages that still described Steel as present, running or configured: - systems/browser-backend.md (incl. gateway-restart env-var note) - comparisons/steel-vs-camoufox.md, comparisons/camoufox-vs-chrome.md - decisions/rollback-steel-to-camofox.md, decisions/index.md - infrastructure/docker-services.md, infrastructure/tailscale.md, infrastructure/hosts.md - systems/homepage-dashboard.md, systems/scheduled-tasks.md - concepts/browser-automation.md, runbooks/recover-docker-service.md - current-state.md, index.md, agents/nanobot.md - log.md (dated entry; supersedes the 00:3x audit's 'endpoint dark' wording) Also restores the Ignis compose row in infrastructure/docker-services.md, which the 2026-10-11 revision dropped (verified: /home/hermes/docker/ignis/docker-compose.yml exists and the ignis container is Up on CT460). Co-Authored-By: Hermes <hermes@local>
5.2 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Docker Services | infrastructure | mixed | 2026-07-22 | 2026-10-29 | 2026-10-29 | high |
|
|
Docker Services
Purpose
Containerized services supporting Hermes and the homelab.
Status
Docker runs on three hosts, and CT460's socket is not readable by the agent user. This page previously claimed "Docker runtime not available" — that is only true for CT460's socket from the hermes user. Real state, verified 2026-10-11:
| Host | Access | Containers running |
|---|---|---|
CT200 docker (100.96.150.69) |
pct exec 200 -- docker ps via PVE |
~50 — main Docker host |
CT333 clawtest (100.122.189.81) |
pct exec 333 -- docker ps via PVE |
8 (gotify, readlater, kokoro-tts, edge-tts, onecli-postgres, …) — the steel-browser container and its image were removed 2026-10-29 |
CT460 hermes |
sudo docker — socket is root:docker srw-rw----, hermes user not in group docker; no passwordless sudo in cron |
ignis (confirmed running; inspect requires root) |
CT200 live inventory (verified 2026-10-11, ~50 containers)
guacamole-guacamole-1, telegram-bot-api, ytdlp-web-player, homarr, overtchat-searxng, searxng, khoj-search-1, prowlarr, overtchat-app, postgres-newsku, guacamole-postgres-1, jellyfin, libre-closet, apprise-api, tt-rss-web-nginx-1, tt-rss-updater-1, tt-rss-app-1, tt-rss-db-1, audiobookshelf, qbittorrent, open-webui, readlater, readlater-extraction-worker, worldmonitor-redis, redis-cache, nextstep-db, nextstep-scheduler-1, nextstep-app, portainer, flaresolverr, sshwifty, 8mblocal, save-restricted-bot, kokoro-tts, edge-tts, filebrowser, filebrowser1, worldmonitor-redis-rest, worldmonitor, overtchat-redis, chromadb, ignis-ignis-1, nc_app_talk_bot_ai, excalidraw-frontend, nc_app_context_agent, portkey-gateway-web-1, guacamole-guacd-1, lobe-chat, mycompose-saas-1.
Watch this one: mycompose-db-1 is in Restarting (1) — a crash-looping database. Flagged for follow-up; root cause not investigated on 2026-10-11.
Note the duplicate Ignis: ignis-ignis-1 on CT200 is a separate deployment from CT460's ignis. See systems/ignis.
CT201 runtipi — Tailscale routes (verified 2026-10-11; Steel routes removed 2026-10-29)
| Host | Path | Target |
|---|---|---|
runtipi.kangaroo-eel.ts.net:8443 (tailnet) |
/ |
http://127.0.0.1:8085 |
/mgr |
http://127.0.0.1:8084 |
|
runtipi.kangaroo-eel.ts.net (tailnet) |
/ |
http://127.0.0.1:8085 |
/mgr |
http://127.0.0.1:8084 |
Correction: this page previously said "Port 443 occupied by Traefik on CT201 — Tailscale uses port 8443 there" and listed CT201's :8443 → localhost:8082 for Homepage. Live tailscale serve status on CT201 shows the target is 127.0.0.1:8085 on both :8443 and the default host. That table also carried a /steel (5173) and /steel-api (3000) pair — both routes were deleted on 2026-10-29 with tailscale serve --set-path <path> off when Steel was removed, so CT201's remaining routes are only / and /mgr on both :443 and :8443. (The /steel-api route never stripped the path prefix — moot now that it is gone.)
Confirmed Compose Files
| File | Path | Services |
|---|---|---|
| Hermes Agent | /home/hermes/.hermes/hermes-agent/docker-compose.yml |
hermes, hermes-dashboard |
| Hermes WebUI | /home/hermes/hermes-webui/docker-compose.yml |
webui |
| ReadLater | /home/hermes/workspace/readlater/docker-compose.yml |
readlater, edge-tts, kokoro-tts |
| Ignis | /home/hermes/docker/ignis/docker-compose.yml (CT460) |
ignis, ignis-data, ignis-obsidian-app |
Steel Browser — removed 2026-10-29. The CT201 compose file and Dockerfile are no longer live: the project
dir /root/steel-browser was deleted along with its containers, images and network. Both files are archived at
/root/_archived-steel/ on CT201 (with /root/_archived-steel/steel-cache-archive-20261029.tgz), and the
images remain re-pullable from ghcr.io. → comparisons/steel-vs-camoufox
Service Definitions (from compose files)
hermes-agent
- Images:
hermes-agent - Containers:
hermes,hermes-dashboard - Volumes: present (paths unverified)
- Environment: present (values unverified — secrets redacted)
hermes-webui
- Ports: present (specific ports unverified)
- Volumes: present
readlater
- Container:
readlater - Ports: present
- Volumes: present
- Dependencies:
edge-tts(travisvn/openai-edge-tts),kokoro-tts(ghcr.io/remsky/kokoro-fastapi-cpu:v0.2.1)
Known Issues
- Docker runtime unavailable on inspection host — service state unknown
- Specific ports, volumes, and env vars not extracted from compose files during this pass
Additional Services (CT201 runtipi)
- Homepage — Dashboard at port 8082 (Tailscale:
https://runtipi.kangaroo-eel.ts.net:8443/) - Manager — Web UI for Homepage at port 8084
- See systems/homepage-dashboard.md for full docs