starred/act
1
0
Fork 0
mirror of https://github.com/nektos/act.git synced 2026-04-26 09:25:54 +03:00
Code Issues 289 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #300] if one job fails, the next run complains about volume is still in use #212

New issue
Closed
opened 2026-03-01 21:41:18 +03:00 by kerem · 15 comments
kerem commented 2026-03-01 21:41:18 +03:00
Owner
Copy link

Originally created by @xsteadfastx on GitHub (Jul 2, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/300

Version: 0.2.10

its about this workflow file. the tests are failing right now and thats ok so far. but if i run act again it complains about the docker volume is still in use.

$ act -v push
DEBU[0000] Loading environment from /home/marv/wip/carson/.env
DEBU[0000] Loading secrets from
DEBU[0000] Loading workflows from '/home/marv/wip/carson/.github/workflows'
DEBU[0000] Reading workflow '/home/marv/wip/carson/.github/workflows/push.yml'
DEBU[0000] Planning event: push
DEBU[0000] Loading slug from git directory '/home/marv/wip/carson/.git'
DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37
DEBU[0000] Loading revision from git directory '/home/marv/wip/carson/.git'
DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37
DEBU[0000] HEAD points to 'c2721305e3b61c33ec3f8f9420c3837c0cab8d37'
DEBU[0000] HEAD matches refs/heads/dev
DEBU[0000] using github ref: refs/heads/dev
DEBU[0000] context env => map[]
DEBU[0000] Loading slug from git directory '/home/marv/wip/carson/.git'
DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37
DEBU[0000] Loading revision from git directory '/home/marv/wip/carson/.git'
DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37
DEBU[0000] HEAD points to 'c2721305e3b61c33ec3f8f9420c3837c0cab8d37'
DEBU[0000] HEAD matches refs/heads/dev
DEBU[0000] using github ref: refs/heads/dev
DEBU[0000] context env => map[]
[push/test] 🚀  Start image=node:12.6-buster-slim
DEBU[0000] Loading slug from git directory '/home/marv/wip/carson/.git'
[push/lint] 🚀  Start image=node:12.6-buster-slim
DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37
DEBU[0000] Loading revision from git directory '/home/marv/wip/carson/.git'
DEBU[0000] Loading slug from git directory '/home/marv/wip/carson/.git'
DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37
DEBU[0000] HEAD points to 'c2721305e3b61c33ec3f8f9420c3837c0cab8d37'
DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37
DEBU[0000] HEAD matches refs/heads/dev
DEBU[0000] Loading revision from git directory '/home/marv/wip/carson/.git'
DEBU[0000] using github ref: refs/heads/dev
DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37
DEBU[0000] HEAD points to 'c2721305e3b61c33ec3f8f9420c3837c0cab8d37'
[push/test]   🐳  docker pull node:12.6-buster-slim
DEBU[0000] HEAD matches refs/heads/dev
DEBU[0000] using github ref: refs/heads/dev
[push/lint]   🐳  docker pull node:12.6-buster-slim
DEBU[0000] Image exists? true
DEBU[0000] Image exists? true
[push/lint]   🐳  docker volume rm act-push-lint
[push/test]   🐳  docker create image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768]
DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768]
DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768]
DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768]
DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768]
DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768]
DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768]
Error: Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768]

$ docker ps -a
CONTAINER ID        IMAGE                            COMMAND             CREATED             STATUS                      PORTS               NAMES
e5a5d94510a0        golangci/golangci-lint:v1.27.0   "make lint"         20 minutes ago      Exited (0) 19 minutes ago                       act-push-lint-1
Originally created by @xsteadfastx on GitHub (Jul 2, 2020). Original GitHub issue: https://github.com/nektos/act/issues/300 Version: 0.2.10 its about [this](https://github.com/xsteadfastx/carson/blob/dev/.github/workflows/push.yml) workflow file. the tests are failing right now and thats ok so far. but if i run `act` again it complains about the docker volume is still in use. ``` $ act -v push DEBU[0000] Loading environment from /home/marv/wip/carson/.env DEBU[0000] Loading secrets from DEBU[0000] Loading workflows from '/home/marv/wip/carson/.github/workflows' DEBU[0000] Reading workflow '/home/marv/wip/carson/.github/workflows/push.yml' DEBU[0000] Planning event: push DEBU[0000] Loading slug from git directory '/home/marv/wip/carson/.git' DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37 DEBU[0000] Loading revision from git directory '/home/marv/wip/carson/.git' DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37 DEBU[0000] HEAD points to 'c2721305e3b61c33ec3f8f9420c3837c0cab8d37' DEBU[0000] HEAD matches refs/heads/dev DEBU[0000] using github ref: refs/heads/dev DEBU[0000] context env => map[] DEBU[0000] Loading slug from git directory '/home/marv/wip/carson/.git' DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37 DEBU[0000] Loading revision from git directory '/home/marv/wip/carson/.git' DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37 DEBU[0000] HEAD points to 'c2721305e3b61c33ec3f8f9420c3837c0cab8d37' DEBU[0000] HEAD matches refs/heads/dev DEBU[0000] using github ref: refs/heads/dev DEBU[0000] context env => map[] [push/test] 🚀 Start image=node:12.6-buster-slim DEBU[0000] Loading slug from git directory '/home/marv/wip/carson/.git' [push/lint] 🚀 Start image=node:12.6-buster-slim DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37 DEBU[0000] Loading revision from git directory '/home/marv/wip/carson/.git' DEBU[0000] Loading slug from git directory '/home/marv/wip/carson/.git' DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37 DEBU[0000] HEAD points to 'c2721305e3b61c33ec3f8f9420c3837c0cab8d37' DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37 DEBU[0000] HEAD matches refs/heads/dev DEBU[0000] Loading revision from git directory '/home/marv/wip/carson/.git' DEBU[0000] using github ref: refs/heads/dev DEBU[0000] Found revision: c2721305e3b61c33ec3f8f9420c3837c0cab8d37 DEBU[0000] HEAD points to 'c2721305e3b61c33ec3f8f9420c3837c0cab8d37' [push/test] 🐳 docker pull node:12.6-buster-slim DEBU[0000] HEAD matches refs/heads/dev DEBU[0000] using github ref: refs/heads/dev [push/lint] 🐳 docker pull node:12.6-buster-slim DEBU[0000] Image exists? true DEBU[0000] Image exists? true [push/lint] 🐳 docker volume rm act-push-lint [push/test] 🐳 docker create image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[] DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768] DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768] DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768] DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768] DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768] DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768] DEBU[0000] Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768] Error: Error response from daemon: remove act-push-lint: volume is in use - [e5a5d94510a022c8c5c16b0130aa6ca3736ad36c9669350c1300f0e1dc962768] ``` ``` $ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e5a5d94510a0 golangci/golangci-lint:v1.27.0 "make lint" 20 minutes ago Exited (0) 19 minutes ago act-push-lint-1 ```
kerem 2026-03-01 21:41:18 +03:00
  • closed this issue
  • added the
    stale
         label
kerem commented 2026-03-01 21:41:19 +03:00
Author
Owner
Copy link

@xsteadfastx commented on GitHub (Jul 4, 2020):

i installed the master version and i have the feeling it works. maybe i stepped into #186.

<!-- gh-comment-id:653727919 --> @xsteadfastx commented on GitHub (Jul 4, 2020): i installed the master version and i have the feeling it works. maybe i stepped into #186.
kerem commented 2026-03-01 21:41:19 +03:00
Author
Owner
Copy link

@xsteadfastx commented on GitHub (Jul 6, 2020):

nope... just got the volume is in use error again.

<!-- gh-comment-id:654109238 --> @xsteadfastx commented on GitHub (Jul 6, 2020): nope... just got the `volume is in use` error again.
kerem commented 2026-03-01 21:41:19 +03:00
Author
Owner
Copy link

@xsteadfastx commented on GitHub (Jul 7, 2020):

another discovery:

when running two jobs... one is failing there is no cleanup or something of the one good job still running. maybe act should wait for all jobs finishing and after that complaining about a failed jobs. now it looks like its just stops the act process... no matter what.

<!-- gh-comment-id:654807191 --> @xsteadfastx commented on GitHub (Jul 7, 2020): another discovery: when running two jobs... one is failing there is no cleanup or something of the one good job still running. maybe act should wait for all jobs finishing and after that complaining about a failed jobs. now it looks like its just stops the act process... no matter what.
kerem commented 2026-03-01 21:41:19 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Sep 6, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

<!-- gh-comment-id:687680024 --> @github-actions[bot] commented on GitHub (Sep 6, 2020): Issue is stale and will be closed in 7 days unless there is new activity
kerem commented 2026-03-01 21:41:19 +03:00
Author
Owner
Copy link

@devnix commented on GitHub (Sep 23, 2020):

I had to remove the container listed in docker ps -a

<!-- gh-comment-id:697362049 --> @devnix commented on GitHub (Sep 23, 2020): I had to remove the container listed in `docker ps -a`
kerem commented 2026-03-01 21:41:19 +03:00
Author
Owner
Copy link

@xsteadfastx commented on GitHub (Sep 24, 2020):

thats the point... i have to do this always when a job fails!

<!-- gh-comment-id:698589942 --> @xsteadfastx commented on GitHub (Sep 24, 2020): thats the point... i have to do this always when a job fails!
kerem commented 2026-03-01 21:41:20 +03:00
Author
Owner
Copy link

@sebastian-palma commented on GitHub (Nov 19, 2020):

docker -rm ...

<!-- gh-comment-id:730688454 --> @sebastian-palma commented on GitHub (Nov 19, 2020): `docker -rm ...`
kerem commented 2026-03-01 21:41:20 +03:00
Author
Owner
Copy link

@xsteadfastx commented on GitHub (Nov 20, 2020):

yeah... whats the point to have to do this on every failed step? am i holding it wrong?

<!-- gh-comment-id:731104136 --> @xsteadfastx commented on GitHub (Nov 20, 2020): yeah... whats the point to have to do this on every failed step? am i holding it wrong?
kerem commented 2026-03-01 21:41:20 +03:00
Author
Owner
Copy link

@zyndagj commented on GitHub (Nov 22, 2020):

Reporting that this issue still exists in version 0.2.17

<!-- gh-comment-id:731774060 --> @zyndagj commented on GitHub (Nov 22, 2020): Reporting that this issue still exists in version 0.2.17
kerem commented 2026-03-01 21:41:20 +03:00
Author
Owner
Copy link

@devnix commented on GitHub (Nov 24, 2020):

Can someone please reopen this?

<!-- gh-comment-id:733012640 --> @devnix commented on GitHub (Nov 24, 2020): Can someone please reopen this?
kerem commented 2026-03-01 21:41:20 +03:00
Author
Owner
Copy link

@att14 commented on GitHub (Mar 6, 2021):

This appears to still be an issue in 0.2.20. Except in my experience it doesn't even cleanup the volume when the run is successful.

Here is a simple reproduction:

---
name: test-act-cleanup
on: push

jobs:
  test-act:
    name: Test act cleanup
    runs-on: ubuntu-latest
    steps:
      - name: Setup MongoDB
        uses: supercharge/mongodb-github-action@1.3.0
        with:
          mongodb-version: '4.4'

The second time running act will fail with:

| docker: Error response from daemon: Conflict. The container name "/mongodb" is already in use by container "d3c593b6638a09499e095a89817c0c3f88cab8177aacb43a4000fb8370741558". You have to remove (or rename) that container to be able to reuse that name.

I'm running this on macOS 10.15.7 if that matters.

<!-- gh-comment-id:792005110 --> @att14 commented on GitHub (Mar 6, 2021): This appears to still be an issue in 0.2.20. Except in my experience it doesn't even cleanup the volume when the run is successful. Here is a simple reproduction: ``` --- name: test-act-cleanup on: push jobs: test-act: name: Test act cleanup runs-on: ubuntu-latest steps: - name: Setup MongoDB uses: supercharge/mongodb-github-action@1.3.0 with: mongodb-version: '4.4' ``` The second time running `act` will fail with: ``` | docker: Error response from daemon: Conflict. The container name "/mongodb" is already in use by container "d3c593b6638a09499e095a89817c0c3f88cab8177aacb43a4000fb8370741558". You have to remove (or rename) that container to be able to reuse that name. ``` I'm running this on macOS 10.15.7 if that matters.
kerem commented 2026-03-01 21:41:20 +03:00
Author
Owner
Copy link

@bixu commented on GitHub (Mar 17, 2021):

I'm also seeing this behavior. I usually need to restart macOS Docker as a workaround.

<!-- gh-comment-id:800908135 --> @bixu commented on GitHub (Mar 17, 2021): I'm also seeing this behavior. I usually need to restart macOS Docker as a workaround.
kerem commented 2026-03-01 21:41:20 +03:00
Author
Owner
Copy link

@dannykopping commented on GitHub (Nov 6, 2024):

docker container prune works if you don't see any running act container.

<!-- gh-comment-id:2459111658 --> @dannykopping commented on GitHub (Nov 6, 2024): `docker container prune` works if you don't see any running `act` container.
kerem commented 2026-03-01 21:41:20 +03:00
Author
Owner
Copy link

@iustin94 commented on GitHub (Feb 10, 2025):

Stil is an issue. On top of that after stoping manually any running container and doing "docker container prune" I still get the error "no such volume". At this stage, I'm just going to take my changes with the github runners dirrectly.

<!-- gh-comment-id:2649260266 --> @iustin94 commented on GitHub (Feb 10, 2025): Stil is an issue. On top of that after stoping manually any running container and doing "docker container prune" I still get the error "no such volume". At this stage, I'm just going to take my changes with the github runners dirrectly.
kerem commented 2026-03-01 21:41:20 +03:00
Author
Owner
Copy link

@gustavorps commented on GitHub (Oct 29, 2025):

Stil is an issue. On top of that after stoping manually any running container and doing "docker container prune" I still get the error "no such volume". At this stage, I'm just going to take my changes with the github runners dirrectly.

Same

% act --version                       
act version 0.2.82

% docker --version
Docker version 28.3.3, build 980b856

% sw_vers
ProductName:            macOS
ProductVersion:         15.0.1
BuildVersion:           24A348
<!-- gh-comment-id:3462437533 --> @gustavorps commented on GitHub (Oct 29, 2025): > Stil is an issue. On top of that after stoping manually any running container and doing "docker container prune" I still get the error "no such volume". At this stage, I'm just going to take my changes with the github runners dirrectly. Same ```shell % act --version act version 0.2.82 % docker --version Docker version 28.3.3, build 980b856 % sw_vers ProductName: macOS ProductVersion: 15.0.1 BuildVersion: 24A348 ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dependabot/go_modules/github.com/go-git/go-git/v5-5.18.0
dependabot/go_modules/dependencies-08815e2262
mergify/configuration-deprecated-update
dependabot/github_actions/dependencies-a3a104477f
chore/simplify-ci-and-makefile
dependabot/go_modules/golang.org/x/crypto-0.45.0
dependabot/go_modules/github.com/go-viper/mapstructure/v2-2.4.0
panekj/ci/improve-jobs
fix-skip-non-yaml-files-in-dir
normalize-pull-rebuild-flags
fix-no-recurse-by-default
2517-poor-error-for-incomplete-action-step
2472-make-use-new-action-cache-the-new-default-for-downloading-actions
act-tart
act-lxc
act-oidc
act-dind
avoid-slash-in-actor
dependabot/go_modules/github.com/docker/docker-26.1.4incompatible
meta-keep-filetime
local-repository-action-cache
pr-merger
update-docker-deps
follow_local_action_symlink
boltdb-lock-in-handler
use-socket-path
no-pull-no-rebuild
path-issues
fix/env
feat/podman
refactor/testdata
v0.2.87
v0.2.86
v0.2.85
v0.2.84
v0.2.83
v0.2.82
v0.2.81
v0.2.80
v0.2.79
v0.2.78
v0.2.77
v0.2.76
v0.2.75
v0.2.74
v0.2.73
v0.2.72
v0.2.71
v0.2.70
v0.2.69
v0.2.68
v0.2.67
v0.2.66
v0.2.65
v0.2.64
v0.2.63
v0.2.62
v0.2.61
v0.2.60
v0.2.59
v0.2.58
v0.2.57
v0.2.56
v0.2.55
v0.2.54
v0.2.53
v0.2.52
v0.2.51
v0.2.50
v0.2.49
v0.2.48
v0.2.47
v0.2.46
v0.2.45
v0.2.44
v0.2.43
v0.2.42
v0.2.41
v0.2.40
v0.2.39
v0.2.38
v0.2.37
v0.2.36
v0.2.35
v0.2.34
v0.2.33
v0.2.32
v0.2.31
v0.2.30
v0.2.29
v0.2.28
v0.2.27
v0.2.26
v0.2.25
v0.2.24
v0.2.23
v0.2.22
v0.2.21
v0.2.20
v0.2.19
v0.2.18
v0.2.17
v0.2.16
v0.2.15
v0.2.14
v0.2.13
v0.2.12
v0.2.11
v0.2.10
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.3
v0.1.2
v0.1.1
v0.1.0
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
review/not-planned

   
size/M

   
size/XL

   
size/XXL

   
stale

   
stale-exempt
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#212
No description provided.