Skip to content

fix: stop containers before rebuild to avoid name conflict on deploy#26

Merged
SPerekrestova merged 1 commit intomainfrom
fix/deploy-container-conflict
Mar 25, 2026
Merged

fix: stop containers before rebuild to avoid name conflict on deploy#26
SPerekrestova merged 1 commit intomainfrom
fix/deploy-container-conflict

Conversation

@SPerekrestova
Copy link
Copy Markdown
Owner

Summary

  • docker compose up -d --build was failing with "container name already in use" because a stopped container from the previous deploy was still registered
  • Add docker compose down --remove-orphans before the rebuild to cleanly remove all containers first

Root Cause

The deploy script went straight to docker compose up --build without stopping existing containers. When a container ends up in a stopped/stuck state between deploys, Docker rejects the new container creation with a name conflict.

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@SPerekrestova SPerekrestova self-assigned this Mar 25, 2026
@SPerekrestova SPerekrestova merged commit 8940edb into main Mar 25, 2026
3 checks passed
@SPerekrestova SPerekrestova deleted the fix/deploy-container-conflict branch March 25, 2026 12:00
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