mirror of
https://github.com/Memo-2023/mana-monorepo.git
synced 2026-05-14 20:41:09 +02:00
🐛 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:
parent
23c2d85f6e
commit
582c6f58a4
2 changed files with 23 additions and 6 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue