Install docker on ser8 so logdy/dozzle converge there #422

New issue

Open

opened 2026-07-01 09:04:49 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-01 09:04:49 +00:00

Member

Follow-up from 909bac2 (logdy/dozzle enabled on the linux group).

The dozzle + logdy roles gate on command -v docker, so on ser8 they no-op today: ser8 has no docker CLI (verified 2026-07-01). kai-server (docker 29.3.1) brings both loopback UIs up on next converge; ser8 stays skipped until docker lands.

To finish linux compat on ser8 either:

declare docker for the linux group (or a ser8-specific var) and let a role install the engine, or
decide ser8 should not run the container viewers and gate the enable off ser8 explicitly.

ser8 runs the forgejo runner + fleet-converge timer, so docker there is plausibly useful beyond these two UIs. No agent SSH; this is a hands-on-keyboard install or an ansible role addition.

Follow-up from 909bac2 (logdy/dozzle enabled on the linux group). The dozzle + logdy roles gate on `command -v docker`, so on ser8 they no-op today: ser8 has no docker CLI (verified 2026-07-01). kai-server (docker 29.3.1) brings both loopback UIs up on next converge; ser8 stays skipped until docker lands. To finish linux compat on ser8 either: - declare docker for the linux group (or a ser8-specific var) and let a role install the engine, or - decide ser8 should not run the container viewers and gate the enable off ser8 explicitly. ser8 runs the forgejo runner + fleet-converge timer, so docker there is plausibly useful beyond these two UIs. No agent SSH; this is a hands-on-keyboard install or an ansible role addition.

coilyco-ops commented

2026-07-01 09:25:22 +00:00

Author

Member

Reverted the linux enablement in 96e36ed after a bare ward exec ansible-sync (now sweeps local + fleet) surfaced that the roles do not converge cleanly on linux:

ser8: no docker CLI (original finding) - dozzle/logdy skip gracefully.
kai-server (docker 29.3.1 present): dozzle: Bring up dozzle runs DOZZLE_PORT=8080 docker compose up -d and fails with:
```
open /home/kai/.config/dozzle/compose.yaml: permission denied
```
The Install the compose file copy (as user kai, mode 0644) succeeds, but docker compose then can't read it. logdy would hit the same wall. Likely a kai-server docker specifics issue (rootless / userns remap, home-dir traversal perms, or the daemon reading the file under a remapped uid) - needs hands-on investigation on the box.

Why the revert mattered: left enabled, the ser8 fleet-converge timer (full sync vs kai-server every 30m) would fail each tick and fire recurring high-priority Telegram alerts.

To re-enable dozzle/logdy on linux: (1) make the roles converge cleanly on kai-server (root-cause the compose.yaml permission-denied), then (2) get docker onto ser8. Only then flip dozzle_enabled/logdy_enabled back on in group_vars/linux.yml.

Reverted the linux enablement in 96e36ed after a bare `ward exec ansible-sync` (now sweeps local + fleet) surfaced that the roles do not converge cleanly on linux: - **ser8**: no docker CLI (original finding) - dozzle/logdy skip gracefully. - **kai-server** (docker 29.3.1 present): `dozzle: Bring up dozzle` runs `DOZZLE_PORT=8080 docker compose up -d` and fails with: ``` open /home/kai/.config/dozzle/compose.yaml: permission denied ``` The `Install the compose file` copy (as user kai, mode 0644) succeeds, but `docker compose` then can't read it. logdy would hit the same wall. Likely a kai-server docker specifics issue (rootless / userns remap, home-dir traversal perms, or the daemon reading the file under a remapped uid) - needs hands-on investigation on the box. Why the revert mattered: left enabled, the ser8 fleet-converge timer (full sync vs kai-server every 30m) would fail each tick and fire recurring high-priority Telegram alerts. **To re-enable dozzle/logdy on linux:** (1) make the roles converge cleanly on kai-server (root-cause the compose.yaml permission-denied), then (2) get docker onto ser8. Only then flip `dozzle_enabled`/`logdy_enabled` back on in `group_vars/linux.yml`.

coilyco-ops added the

consult

labels

2026-07-02 07:22:22 +00:00

coilyco-ops added

interactive

and removed

consult

labels

2026-07-09 21:46:22 +00:00

coilyco-ops added

headless