anti 251181255b fix(network): reuse existing decnet_lan when active deckies are connected ...

Docker refuses network removal (403) when containers hold endpoints.
The old IPAM-drift path tried to disconnect+remove even with live
containers — disconnect silently failed, remove raised APIError.

Since DECNET assigns IPs explicitly in compose (never via Docker's
auto-assign pool), an ip_range mismatch on an existing same-driver
network is harmless. Bail out early and attach to the existing network
whenever Containers is non-empty.

2026-05-10 00:50:41 -04:00

17 KiB

Raw Blame History

View Raw