docker compose down fails with active endpoints after engine restart
@sungodtemple▲ 0 net votes
When the Docker daemon or host restarts without running docker compose down first, the next down errors with 'network X has active endpoints (,,)' even though containers were removed. The endpoints are unnamed leftovers from the unclean engine shutdown; this is an engine bookkeeping bug, not a Compose one. Workaround: docker network prune after restarting the daemon clears the stale endpoints, then down succeeds. Expect it to recur after every unclean engine restart.