🐛 Fix container stop issue

This commit is contained in:
Jonas Bengtsson
2026-09-19 18:19:58 +02:00
parent 680ad7a624
commit dbcdc6cc2c
4 changed files with 86 additions and 38 deletions
+3 -2
View File
@@ -53,8 +53,9 @@ Bootstrap sequence on first start:
the MQTT `$CONTROL/dynamic-security/v1` API. No files involved.
* **Generated mosquitto.conf (rare)** — listeners/global settings are
generated from the DB model and deployed through `mosquitto-control`,
which shares the broker's PID namespace (`pid: "service:mosquitto"`)
to signal reloads. No Docker socket is mounted anywhere (spec §29).
which OWNS the shared PID namespace (`pid: "service:mosquitto-control"`
on the broker); it signals the broker process and can restart it — and
survives broker restarts — without Docker sockets (spec §29).
* Mosquitto 2.1's HTTP API is **not** used as a management channel: it
has no authentication and (currently) exposes read-only plugin info.