[GH-ISSUE #168] Unhelpful error message when Docker is not running #110

Closed
opened 2026-03-01 21:40:13 +03:00 by kerem · 7 comments
Owner

Originally created by @MaxDesiatov on GitHub (Mar 21, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/168

On macOS, when Docker is not running the error message doesn't say anything about the status of the Docker daemon. With the latest version of act installed via Homebrew the error message is:

% act
[Main/check-labels] 🚀  Start image=node:12.6-buster-slim
Error: unable to determine if image already exists for image "node:12.6-buster-slim"

The action runs normally when Docker is running, it took some time to diagnose this though. I would expect the error message to mention that the connection to the Docker daemon was not established, with a suggestion to start or to install it with a link to Docker installation instructions appropriate for the platform.

Originally created by @MaxDesiatov on GitHub (Mar 21, 2020). Original GitHub issue: https://github.com/nektos/act/issues/168 On macOS, when Docker is not running the error message doesn't say anything about the status of the Docker daemon. With the latest version of `act` installed via Homebrew the error message is: ``` % act [Main/check-labels] 🚀 Start image=node:12.6-buster-slim Error: unable to determine if image already exists for image "node:12.6-buster-slim" ``` The action runs normally when Docker is running, it took some time to diagnose this though. I would expect the error message to mention that the connection to the Docker daemon was not established, with a suggestion to start or to install it with a link to Docker installation instructions appropriate for the platform.
kerem 2026-03-01 21:40:13 +03:00
Author
Owner

@jarektkaczyk commented on GitHub (Mar 22, 2020):

2nd that, just got here with the same symptoms
thanks @MaxDesiatov for posting, helped me resolve mine quickly

<!-- gh-comment-id:602154685 --> @jarektkaczyk commented on GitHub (Mar 22, 2020): 2nd that, just got here with the same symptoms thanks @MaxDesiatov for posting, helped me resolve mine quickly
Author
Owner

@jbeveland27 commented on GitHub (Mar 23, 2020):

Same experience here. Additionally, I think it might be helpful to indicate in the README that Docker is both required to be installed locally and running for this to work.

Thanks to @MaxDesiatov for posting!

<!-- gh-comment-id:602305499 --> @jbeveland27 commented on GitHub (Mar 23, 2020): Same experience here. Additionally, I think it might be helpful to indicate in the README that Docker is both required to be installed locally and running for this to work. Thanks to @MaxDesiatov for posting!
Author
Owner

@chrisluedtke commented on GitHub (Mar 26, 2020):

Not macOS, but I also saw this message and I needed to sudo act.

Installed via:

curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bash

Other details:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 19.10
Release:	19.10
Codename:	eoan

$ docker --version
Docker version 19.03.8, build afacb8b7f0
<!-- gh-comment-id:604465347 --> @chrisluedtke commented on GitHub (Mar 26, 2020): Not macOS, but I also saw this message and I needed to `sudo act`. Installed via: ``` curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bash ``` Other details: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan $ docker --version Docker version 19.03.8, build afacb8b7f0 ```
Author
Owner

@AdrianoCahete commented on GitHub (Mar 30, 2020):

Same on Windows 10.

<!-- gh-comment-id:606290149 --> @AdrianoCahete commented on GitHub (Mar 30, 2020): Same on Windows 10.
Author
Owner

@neilswinton commented on GitHub (Apr 15, 2020):

I'm seeing this while running inside in a container. In my container, docker is exposed using TCP port 2375. The code seems to look for /var/run/docker.sock even when DOCKER_HOST=host.docker.internal:2375. Since there's no /var/run/docker.sock the listing of images fails along with all other access to docker. Docker commands succeed because they honor DOCKER_HOST. I realize this is not a mainstream issue...

<!-- gh-comment-id:614199775 --> @neilswinton commented on GitHub (Apr 15, 2020): I'm seeing this while running inside in a container. In my container, docker is exposed using TCP port 2375. The code seems to look for /var/run/docker.sock even when DOCKER_HOST=host.docker.internal:2375. Since there's no /var/run/docker.sock the listing of images fails along with all other access to docker. Docker commands succeed because they honor DOCKER_HOST. I realize this is not a mainstream issue...
Author
Owner

@cplee commented on GitHub (Apr 23, 2020):

fixed by github.com/nektos/act@6c4e7b9fde

<!-- gh-comment-id:618197946 --> @cplee commented on GitHub (Apr 23, 2020): fixed by https://github.com/nektos/act/commit/6c4e7b9fdedeeeb1eda78cefaff55750033d1327
Author
Owner

@kiptoomm commented on GitHub (Aug 16, 2020):

For anyone like me who was still getting this error message, ensure docker is installed and running

<!-- gh-comment-id:674508168 --> @kiptoomm commented on GitHub (Aug 16, 2020): For anyone like me who was still getting this error message, ensure [docker is installed and running](https://stackoverflow.com/questions/40523307/brew-install-docker-does-not-include-docker-engine)
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#110
No description provided.