[GH-ISSUE #443] docker/build-push-action@v2 not working #308

Closed
opened 2026-03-01 21:42:14 +03:00 by kerem · 9 comments
Owner

Originally created by @stefanfoulis on GitHub (Dec 9, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/443

Act works ok for me locally with some examples I tried. But when I try to use the official docker actions (v2) it does not work for me (macOS with Docker for Mac).

When following examples from https://github.com/marketplace/actions/build-and-push-docker-images I get these errors:

❗  ::error::Unable to locate executable file: docker. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
[...] 🚀  Start image=node:12.6-buster-slim
[...]   🐳  docker run image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[...]   🐳  docker cp src=/Users/stefanfoulis/Coding/Sherpany/obrv2-localdev-attempt2/. dst=/github/workspace
[...] ⭐  Run Checkout
[...]   ✅  Success - Checkout
[...] ⭐  Run Set up QEMU
[...]   ☁  git clone 'https://github.com/docker/setup-qemu-action' # ref=v1
[...]   🐳  docker cp src=/Users/stefanfoulis/.cache/act/docker-setup-qemu-action@v1 dst=/actions/
| 💎 Installing QEMU static binaries...
[...]   ❗  ::error::Unable to locate executable file: docker. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
[...]   ❌  Failure - Set up QEMU
Error: exit with `FAILURE`: 1

The same error appear with all these actions:

  • docker/setup-qemu-action@v1
  • docker/setup-buildx-action@v1
  • docker/login-action@v1
  • docker/build-push-action@v2

The same workflow file works on github though.

Originally created by @stefanfoulis on GitHub (Dec 9, 2020). Original GitHub issue: https://github.com/nektos/act/issues/443 Act works ok for me locally with some examples I tried. But when I try to use the official docker actions (v2) it does not work for me (macOS with Docker for Mac). When following examples from https://github.com/marketplace/actions/build-and-push-docker-images I get these errors: ``` ❗ ::error::Unable to locate executable file: docker. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable. ``` ``` [...] 🚀 Start image=node:12.6-buster-slim [...] 🐳 docker run image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[] [...] 🐳 docker cp src=/Users/stefanfoulis/Coding/Sherpany/obrv2-localdev-attempt2/. dst=/github/workspace [...] ⭐ Run Checkout [...] ✅ Success - Checkout [...] ⭐ Run Set up QEMU [...] ☁ git clone 'https://github.com/docker/setup-qemu-action' # ref=v1 [...] 🐳 docker cp src=/Users/stefanfoulis/.cache/act/docker-setup-qemu-action@v1 dst=/actions/ | 💎 Installing QEMU static binaries... [...] ❗ ::error::Unable to locate executable file: docker. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable. [...] ❌ Failure - Set up QEMU Error: exit with `FAILURE`: 1 ``` The same error appear with all these actions: - `docker/setup-qemu-action@v1` - `docker/setup-buildx-action@v1` - `docker/login-action@v1` - `docker/build-push-action@v2` The same workflow file works on github though.
kerem closed this issue 2026-03-01 21:42:15 +03:00
Author
Owner

@catthehacker commented on GitHub (Dec 9, 2020):

https://github.com/nektos/act#default-runners-are-intentionally-incomplete
https://github.com/nektos/act/issues/107
Docker is not included in the image

<!-- gh-comment-id:741870275 --> @catthehacker commented on GitHub (Dec 9, 2020): https://github.com/nektos/act#default-runners-are-intentionally-incomplete https://github.com/nektos/act/issues/107 Docker is not included in the image
Author
Owner

@stefanfoulis commented on GitHub (Dec 9, 2020):

/me begins 18GB download over 4G connection 🤞 😅

<!-- gh-comment-id:741872470 --> @stefanfoulis commented on GitHub (Dec 9, 2020): /me begins 18GB download over 4G connection 🤞 😅
Author
Owner

@tomkerkhove commented on GitHub (Dec 22, 2020):

I went that route as well until Docker ran out of space 🙈

<!-- gh-comment-id:749434563 --> @tomkerkhove commented on GitHub (Dec 22, 2020): I went that route as well until Docker ran out of space 🙈
Author
Owner

@github-actions[bot] commented on GitHub (Jan 22, 2021):

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

<!-- gh-comment-id:765041550 --> @github-actions[bot] commented on GitHub (Jan 22, 2021): Issue is stale and will be closed in 14 days unless there is new activity
Author
Owner

@JakeChampion commented on GitHub (Jan 27, 2021):

This is also an issue when using the larger image:

act -P ubuntu-18.04=nektos/act-environments-ubuntu:18.04
[Deploy to dev and test/deploy-to-heroku-dev] 🚀  Start image=node:12.6-buster-slim
[Deploy to dev and test/deploy-to-heroku-dev]   🐳  docker run image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[Deploy to dev and test/deploy-to-heroku-dev]   🐳  docker cp src=/Users/jake/Code/polyfill-service/. dst=/github/workspace
[Deploy to dev and test/deploy-to-heroku-dev] ⭐  Run Checkout
[Deploy to dev and test/deploy-to-heroku-dev]   ✅  Success - Checkout
[Deploy to dev and test/deploy-to-heroku-dev] ⭐  Run Prepare
[Deploy to dev and test/deploy-to-heroku-dev]   ⚙  ::set-output:: tags=ghcr.io/financial-times/polyfill-service:edge,registry.heroku.com/origami-polyfill-service-int/web
[Deploy to dev and test/deploy-to-heroku-dev]   ✅  Success - Prepare
[Deploy to dev and test/deploy-to-heroku-dev] ⭐  Run Set up Docker Buildx
[Deploy to dev and test/deploy-to-heroku-dev]   ☁  git clone 'https://github.com/docker/setup-buildx-action' # ref=v1
[Deploy to dev and test/deploy-to-heroku-dev]   🐳  docker cp src=/Users/jake/.cache/act/docker-setup-buildx-action@v1 dst=/actions/
[Deploy to dev and test/deploy-to-heroku-dev]   ❓  ::save-state name=isPost::true
[Deploy to dev and test/deploy-to-heroku-dev]   ❗  ::error::Unable to locate executable file: docker. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
[Deploy to dev and test/deploy-to-heroku-dev]   ❌  Failure - Set up Docker Buildx
Error: exit with `FAILURE`: 1
<!-- gh-comment-id:767933429 --> @JakeChampion commented on GitHub (Jan 27, 2021): This is also an issue when using the larger image: ``` act -P ubuntu-18.04=nektos/act-environments-ubuntu:18.04 [Deploy to dev and test/deploy-to-heroku-dev] 🚀 Start image=node:12.6-buster-slim [Deploy to dev and test/deploy-to-heroku-dev] 🐳 docker run image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[] [Deploy to dev and test/deploy-to-heroku-dev] 🐳 docker cp src=/Users/jake/Code/polyfill-service/. dst=/github/workspace [Deploy to dev and test/deploy-to-heroku-dev] ⭐ Run Checkout [Deploy to dev and test/deploy-to-heroku-dev] ✅ Success - Checkout [Deploy to dev and test/deploy-to-heroku-dev] ⭐ Run Prepare [Deploy to dev and test/deploy-to-heroku-dev] ⚙ ::set-output:: tags=ghcr.io/financial-times/polyfill-service:edge,registry.heroku.com/origami-polyfill-service-int/web [Deploy to dev and test/deploy-to-heroku-dev] ✅ Success - Prepare [Deploy to dev and test/deploy-to-heroku-dev] ⭐ Run Set up Docker Buildx [Deploy to dev and test/deploy-to-heroku-dev] ☁ git clone 'https://github.com/docker/setup-buildx-action' # ref=v1 [Deploy to dev and test/deploy-to-heroku-dev] 🐳 docker cp src=/Users/jake/.cache/act/docker-setup-buildx-action@v1 dst=/actions/ [Deploy to dev and test/deploy-to-heroku-dev] ❓ ::save-state name=isPost::true [Deploy to dev and test/deploy-to-heroku-dev] ❗ ::error::Unable to locate executable file: docker. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable. [Deploy to dev and test/deploy-to-heroku-dev] ❌ Failure - Set up Docker Buildx Error: exit with `FAILURE`: 1 ```
Author
Owner

@catthehacker commented on GitHub (Jan 27, 2021):

@JakeChampion in the log, you still have node:12.6-buster-slim, you probably replaced wrong image/platform.

<!-- gh-comment-id:767943961 --> @catthehacker commented on GitHub (Jan 27, 2021): @JakeChampion in the log, you still have `node:12.6-buster-slim`, you probably replaced wrong image/platform.
Author
Owner

@mandrean commented on GitHub (Feb 24, 2021):

@JakeChampion is your workflow declaring runs-on: ubuntu-latest?

In that case, try:

$ act -P ubuntu-latest=catthehacker/ubuntu:act-latest

If that doesn't work, try

$ act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04
<!-- gh-comment-id:785147953 --> @mandrean commented on GitHub (Feb 24, 2021): @JakeChampion is your workflow declaring `runs-on: ubuntu-latest`? In that case, try: ``` $ act -P ubuntu-latest=catthehacker/ubuntu:act-latest ``` If that doesn't work, try ``` $ act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04 ```
Author
Owner

@github-actions[bot] commented on GitHub (Mar 27, 2021):

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

<!-- gh-comment-id:808605861 --> @github-actions[bot] commented on GitHub (Mar 27, 2021): Issue is stale and will be closed in 14 days unless there is new activity
Author
Owner

@catthehacker commented on GitHub (Mar 30, 2021):

docker cli is included in medium/large image so I think it's safe to close this issue.

<!-- gh-comment-id:809963057 --> @catthehacker commented on GitHub (Mar 30, 2021): `docker` cli is included in `medium`/`large` image so I think it's safe to close this issue.
Sign in to join this conversation.
No milestone
No project
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#308
No description provided.