Detect and bail if there are multiple copies of a service's container running #392
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#392
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A build using
docker-cp-deploy
was failing here: https://git.coopcloud.tech/coop-cloud/docker-cp-deploy/src/branch/main/plugin.sh#L58Seems like this was caused by there being multiple containers running for the service.
We could potentially add a check to
docker-cp-deploy
to bail if this situation is detected.CC @aadil @decentral1se
The strange thing is, I thought
8df80fcd8f/plugin.sh (L44-L49)
was for that? I remember @knoflook raising this issue...Oh good call, thought I remembered some previous discussion but couldn't find it.
Could it be the config in question is using an old version of the image? The new one is here on Gitea: https://git.coopcloud.tech/coop-cloud/-/packages/container/docker-cp-deploy/latest
OK, switched to
git.coopcloud.tech/coop-cloud/docker-cp-deploy
on the affected pipeline and all is well 😌