🐛 fix(ci): prevent container name conflict in staging deployment

- Remove stale containers before deploying (fixes 'name already in use' error)
- Always use --force-recreate flag for consistent deployment behavior
- Add troubleshooting docs for container name conflicts
This commit is contained in:
Wuesteon 2025-12-09 15:59:06 +01:00
parent 23c2d85f6e
commit 582c6f58a4
2 changed files with 23 additions and 6 deletions

View file

@ -543,6 +543,20 @@ docker logs chat-backend-staging --tail 200
# - Port conflicts
```
### Container name conflict error
If you see: `Error: The container name "/xxx-staging" is already in use`
```bash
# SSH to server and remove the stale container
ssh deploy@46.224.108.214
docker rm -f todo-web-staging # Replace with actual container name
# Then re-run the deployment
```
This can happen if a container was created outside of docker-compose or if a previous deployment failed mid-way.
---
## Managing Tags