david
134fd4a0ed
The host's /run/dbus/system_bus_socket is the standard dbus socket for systemd. Bind-mounting the container's socket onto /run/dbus overwrites the host's socket, breaking dockerd's ability to manage cgroups via systemd (manifests as 'org.freedesktop.systemd1 was not provided by any .service files' on subsequent docker run). Use tmpfs instead — ephemeral container-local sockets that don't conflict with host services.
infra/
Full stack configuration as deployed on the RPi 3B+ at 192.168.81.147.
Layout on host
/root/
├── compose.yaml → infra/compose.yaml
├── mosquitto/config/mosquitto.conf → infra/mosquitto/config/mosquitto.conf
├── zigbee2mqtt/ → infra/zigbee2mqtt/
│ ├── configuration.yaml # device pairings + friendly names + groups
│ ├── coordinator_backup.json # zigbee network key + pan id (recovery)
│ └── state.json # per-device persisted state (ON/OFF, etc.)
└── nodered/ → bind-mount for nodered container's /data
├── flows.json → generated from ../flows/zigbee-monitor.yaml
├── settings.js → infra/nodered/settings.js
└── start.sh → infra/nodered/start.sh (patches Dashboard SPA)
Rebuild procedure from a fresh host
- Install Docker,
docker compose. - Clone this repo,
cd infra. mkdir -p mosquitto/data mosquitto/log(empty dirs for the volume mounts).docker compose up -d.- Pair zigbee devices (IEEE addresses in
zigbee2mqtt/configuration.yamlwill be wrong; re-pair or use the existingcoordinator_backup.jsonto rejoin the same network). just deployfrom the repo root to push the Node-RED flow.
Files that drift at runtime
nodered/flows.json— managed by the generator, do not hand-edit.nodered/node_modules/@flowfuse/node-red-dashboard/dist/index.html— patched bystart.shat every container start; survives reboots, lost ondocker compose down -v.mosquitto/data/— broker persistence, transient.zigbee2mqtt/database.db— sqlite, transient (regenerated fromconfiguration.yaml+coordinator_backup.json).zigbee2mqtt/state.json— committed so device ON/OFF state survives full rebuilds.