mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2457] Error: volume is in use #1133
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#1133
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 @GsLogiMaker on GitHub (Sep 12, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2457
Bug report info
Command used with act
Describe issue
I had been debugging my github actions workflow with act for a while and after some tweaking to the workflow file, I suddenly started getting a
volume is in useerror. The workflow consists of two jobs, where the second needs the first to finish. The first completes fine, but the second doesn't start because of the aforementioned error. I didn't change anything substantial, and even after commenting out most of the workflow's code I still get the error.I believe the issue might be because of some kind of internal state stored by act, maybe on the file-system, but I couldn't find any commands to clear out any internal states or caches and I don't know where to look to find them if they do exist.
Link to GitHub repository
https://github.com/GsLogiMaker/glecs_godot_plugin/tree/cpp
Workflow content
Relevant log output
Additional information
I needed to run act as root because of file permission issues surrounding the use of code-server. I still get the same error when running the workflow in my normal file-system home without sudo.
@sebastien-perpignane commented on GitHub (Oct 11, 2024):
Hey,
Try this maybe:
docker ps -a --filter volume=act-Build-Process-run-test-suite-898315f0e00f8ddda9d4f14d4a139d00e0b979c90a05c3b0826ed0c4b5a471a4It should let you know which container is using the volume.
Then you should be able to remove the container using the volume.
@donovanmuller commented on GitHub (Nov 4, 2024):
Same issue, deleted the exited container:
@github-actions[bot] commented on GitHub (May 4, 2025):
Issue is stale and will be closed in 14 days unless there is new activity
@sebthom commented on GitHub (Jun 23, 2025):
I am seeing the same issue on windows using latest act version (0.2.78). I constantly need to manually remove contains. this is quite annoying.