Skip to content

make down: remove orphan containers - #13

Merged
kevrez merged 1 commit into
mainfrom
ops/compose-down-remove-orphans
Jun 17, 2026
Merged

kevrez merged 1 commit into
mainfrom
ops/compose-down-remove-orphans

Conversation

@kevrez

@kevrez kevrez commented Jun 17, 2026

Copy link
Copy Markdown
Owner

What

Add --remove-orphans to the make down target:

down:
	$(COMPOSE) down --remove-orphans

Why

docker compose down only stops/removes services defined in the current compose file. When a service is removed from docker-compose.yml (e.g. retiring the Streamlit dashboard service), its container becomes an orphan that make down leaves running — so the old app stays reachable on its old port and a reload "looks unchanged" even after make down && make up.

Hit this exact case during the front-end cutover: the old workshop-dashboard-1 kept serving :8501 for hours after the service was removed. --remove-orphans cleans these up automatically.

🤖 Generated with Claude Code

`docker compose down` only manages services defined in the current compose
file. When a service is removed (e.g. the retired Streamlit dashboard), its
container is orphaned and keeps running, so the old app stays reachable.
Adding --remove-orphans makes `make down` clean those up.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@kevrez
kevrez merged commit 61a5a39 into main Jun 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant