mirror of
https://github.com/nektos/act.git
synced 2026-04-25 17:05:50 +03:00
[GH-ISSUE #174] Conflict: container name already in use #115
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#115
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @greg0ire on GitHub (Mar 29, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/174
When trying to run
acton https://github.com/doctrine/sql-formatter, I'm getting this output:Note how I have a workflow named
Continuous Integration/Static Analysis with Psalm, and another namedContinuous Integration/Static Analysis with PHPStan. A fix might be to append a hash of the workflow name to the container name, dunno why it's truncated in the first place though. Is there a limit to the length of docker container names?@mwang87 commented on GitHub (Apr 1, 2020):
I ran into this as well. Basically, there is a fixed length they use for the container name. One solution from my side was to shorten the name of workflow name. Not perfect but does work.
@greg0ire commented on GitHub (Apr 1, 2020):
I think the place where to fix this might be in this piece of code:
github.com/nektos/act@4a4bd36cf6/pkg/runner/run_context.go (L276-L298)Also, this SO question says that images have a max length of 30 (but containers don't have a max length for their name): https://stackoverflow.com/a/42642992/353612
@cplee commented on GitHub (Apr 16, 2020):
thanks @albertofem for the PR, merged!
@displague commented on GitHub (Oct 14, 2020):
I encountered the same error message, but it was due to stale containers and volumes.
I used
docker rmon the container that was cited in the error message, and thendocker system prune --volumes --allto get things back in order.