Open GsLogiMaker opened 2 months ago
Hey,
Try this maybe:
docker ps -a --filter volume=act-Build-Process-run-test-suite-898315f0e00f8ddda9d4f14d4a139d00e0b979c90a05c3b0826ed0c4b5a471a4
It should let you know which container is using the volume.
Then you should be able to remove the container using the volume.
Same issue, deleted the exited container:
$ docker ps -a --filter volume=act-xxx-30c9d7d991c0b592bef67343da294c5042c27a4a55765fa4ebc000df27f6bf5c
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0a0d1b51677b danielflook/terraform-github-actions "/entrypoints/validaβ¦" 8 minutes ago Exited (137) 59 seconds ago act-xxx-30c9d7d991c0b592bef67343da294c5042c27a4-535096946b77f9e05d543c3194fc423bdec634726d199f94d2ae0dc92b448fee
$ docker rm 0a0d1b51677b
0a0d1b51677b
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 use
error. 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.