oskar/homelab-codex-ws
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity
homelab-codex-ws/hosts/chelsty-infra/runtime/zigbee2mqtt/docker-compose.override.yml

22 lines
953 B
YAML
Raw Normal View History

Bootstrap CHELSTY runtime stack
2026-05-11 21:36:10 +02:00
services:
zigbee2mqtt:
zigbee2mqtt: use extra_hosts host-gateway instead of network_mode: host docker-compose v1 cannot clear the ports list from the base compose with ports: [] in an override, so network_mode: host caused InvalidArgument. Use extra_hosts with host-gateway instead: maps 'mosquitto' hostname to the Docker bridge gateway IP so mqtt://mosquitto:1883 reaches the host-networked mosquitto process from within the bridge-networked z2m container. Requires Docker 20.10+ (present on chelsty-infra). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-27 15:12:33 +02:00
# mosquitto runs with network_mode: host on chelsty-infra.
# extra_hosts maps the 'mosquitto' hostname to the host gateway IP so that
# mqtt://mosquitto:1883 in configuration.yaml reaches the host-networked
zigbee2mqtt: config goes in data dir (writable), not separate ro mount z2m migrates configuration.yaml on startup and needs write access. Remove the separate :ro config mount; rely on the base compose's /opt/homelab/data/zigbee2mqtt/data:/app/data read-write mount instead. configuration.yaml must exist at that path on the node before first run. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-27 15:13:33 +02:00
# mosquitto process. Requires Docker 20.10+ (present on chelsty-infra).
zigbee2mqtt: use extra_hosts host-gateway instead of network_mode: host docker-compose v1 cannot clear the ports list from the base compose with ports: [] in an override, so network_mode: host caused InvalidArgument. Use extra_hosts with host-gateway instead: maps 'mosquitto' hostname to the Docker bridge gateway IP so mqtt://mosquitto:1883 reaches the host-networked mosquitto process from within the bridge-networked z2m container. Requires Docker 20.10+ (present on chelsty-infra). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-27 15:12:33 +02:00
extra_hosts:
- "mosquitto:host-gateway"
Bootstrap CHELSTY runtime stack
2026-05-11 21:36:10 +02:00
environment:
Fix pending actions: node_exporter, zigbee2mqtt, chelsty-ha monitoring node_exporter (new service): - Add services/node_exporter/docker-compose.yml matching solaria deployment (network_mode: host, pid: host, /:/host:ro,rslave mount) - Add services/node_exporter/service.yaml zigbee2mqtt chelsty-infra override: - Fix network_mode: host (mosquitto runs on host network, port 1883 on localhost) - Fix volume mount: ./configuration.yaml → absolute /opt/homelab/config/zigbee2mqtt/ (secrets stay in runtime config dir, never in Git) - Remove MQTT_USER/MQTT_PASSWORD (mosquitto uses allow_anonymous true) - Extend healthcheck start_period to 60s (z2m takes time on first start) chelsty-ha/services.yaml: - Remove node-agent entry entirely (never deployed, no plans to bootstrap now) - Keep homeassistant with monitor: false (no node-agent = no health events) supervisor: respect monitor: false in services.yaml - Skip action generation for services where monitor=false - Cleans up chelsty-ha entries from action queue without removing desired-state docs Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-27 15:10:48 +02:00
- TZ=Europe/Warsaw
Bootstrap CHELSTY runtime stack
2026-05-11 21:36:10 +02:00
healthcheck:
Fix pending actions: node_exporter, zigbee2mqtt, chelsty-ha monitoring node_exporter (new service): - Add services/node_exporter/docker-compose.yml matching solaria deployment (network_mode: host, pid: host, /:/host:ro,rslave mount) - Add services/node_exporter/service.yaml zigbee2mqtt chelsty-infra override: - Fix network_mode: host (mosquitto runs on host network, port 1883 on localhost) - Fix volume mount: ./configuration.yaml → absolute /opt/homelab/config/zigbee2mqtt/ (secrets stay in runtime config dir, never in Git) - Remove MQTT_USER/MQTT_PASSWORD (mosquitto uses allow_anonymous true) - Extend healthcheck start_period to 60s (z2m takes time on first start) chelsty-ha/services.yaml: - Remove node-agent entry entirely (never deployed, no plans to bootstrap now) - Keep homeassistant with monitor: false (no node-agent = no health events) supervisor: respect monitor: false in services.yaml - Skip action generation for services where monitor=false - Cleans up chelsty-ha entries from action queue without removing desired-state docs Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-27 15:10:48 +02:00
test: ["CMD-SHELL", "wget -qO- http://localhost:8080 > /dev/null 2>&1 || exit 1"]
interval: 30s
timeout: 10s
Bootstrap CHELSTY runtime stack
2026-05-11 21:36:10 +02:00
retries: 3
zigbee2mqtt: config goes in data dir (writable), not separate ro mount z2m migrates configuration.yaml on startup and needs write access. Remove the separate :ro config mount; rely on the base compose's /opt/homelab/data/zigbee2mqtt/data:/app/data read-write mount instead. configuration.yaml must exist at that path on the node before first run. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-27 15:13:33 +02:00
start_period: 90s
# Note: volumes NOT overridden here.
# The base docker-compose.yml mounts /opt/homelab/data/zigbee2mqtt/data:/app/data
# (read-write). configuration.yaml must be placed in that directory on the node:
# /opt/homelab/data/zigbee2mqtt/data/configuration.yaml
# z2m rewrites this file during migrations — read-only mount is not viable.
Reference in a new issue Copy permalink