fix: LXD AppArmor compat + umami port conflict #1

Merged

johba merged 1 commit from fix/lxd-apparmor-compat into master

2026-04-05 15:55:58 +00:00

johba commented

2026-04-05 15:06:04 +00:00

Owner

Summary

Add to all services in docker-compose.yml
Move umami from port 3000 to 3001 to avoid conflict with Forgejo

Why

Docker containers in LXD need AppArmor unconfined to create Unix sockets. Without this, anvil and postgres crash on startup.

Umami and Forgejo both bind port 3000, causing a conflict when running the harb stack alongside the disinto factory.

Test plan

All 10 services come up healthy on harb-dev-box (LXD)
No port conflicts with disinto stack

## Summary - Add to all services in docker-compose.yml - Move umami from port 3000 to 3001 to avoid conflict with Forgejo ## Why Docker containers in LXD need AppArmor unconfined to create Unix sockets. Without this, anvil and postgres crash on startup. Umami and Forgejo both bind port 3000, causing a conflict when running the harb stack alongside the disinto factory. ## Test plan - All 10 services come up healthy on harb-dev-box (LXD) - No port conflicts with disinto stack

johba added 1 commit 2026-04-05 15:06:04 +00:00

fix: add apparmor=unconfined for LXD compat, move umami to port 3001 f072cb81b4

Docker containers running inside LXD need security_opt apparmor=unconfined
to avoid permission denied errors on Unix socket creation (anvil, postgres).

Umami port moved from 3000 to 3001 to avoid conflict with Forgejo when
running alongside the disinto factory stack.