Consistent `Cannot connect to the Docker daemon` issue on CI
See original GitHub issueBehaviour
- I’m getting a consistent error when trying to use the
setup-buildx-action
- The error is consistent in that it happens on each push
- Sometimes it happens for target
x86_64-unknown-linux-gnu
, then sometimes it happens for targetx86_64-apple-darwin
- It has primarily been happening for
x86_64-apple-darwin
- It has primarily been happening for
- Sometimes it happens for target
ERROR: failed to initialize builder builder-a9707d5d-0e81-4fb9-9d1f-4c4408494f56 (builder-a9707d5d-0e81-4fb9-9d1f-4c4408494f560): Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Error: The process '/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/docker-setup-buildx-OSo80H/bin/buildx' failed with exit code 1
Steps to reproduce this issue
- Reproducing exact behavior might be hard
- I have included links to the public action on the public repository however
Expected behaviour
Tell us what should happen
- I expect the simple
setup-buildx-action
to not fail. This failure is new behavior
Actual behaviour
Tell us what happens instead
- I get a very consistent failure related to
docker
not running?
Configuration
- Repository URL (if public): https://github.com/FuelLabs/ci-dummy-test
- Build URL (if public): https://github.com/FuelLabs/ci-dummy-test/actions/runs/3370479770/jobs/5591626591
publish-fuel-indexer-binaries:
name: Release fuel-indexer binaries
runs-on: ${{ matrix.job.os }}
needs:
- cancel-previous-runs
# - cargo-test-workspace-all-features
# - cargo-verifications
# if: github.event_name == 'release' && github.event.action == 'published'
# Only do this job if publishing a release
strategy:
matrix:
job:
# TODO: Add other targets as needed, using fuel-core as reference
- os: ubuntu-latest
platform: linux
target: x86_64-unknown-linux-gnu
cross_image: x86_64-linux-gnu
# - os: macos-latest
# platform: darwin
# target: x86_64-apple-darwin
steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v1
- name: Log in to the ghcr.io registry
uses: docker/login-action@v1
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.repository_owner }}
password: ${{ secrets.GITHUB_TOKEN }}
Logs
Download the log file of your build and attach it to this issue.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Docker in Docker is failing with error - Cannot connect to the ...
Cannot connect to the Docker daemon at tcp://docker:2375/. ... Now, with this CI config, it works consistently five times in a row:.
Read more >How to Resolve the “cannot connect to the Docker daemon ...
Resolving the “cannot connect to the Docker daemon” Error · 1. First, check if the Docker engine is running: sudo service docker status...
Read more >maven - gitlab-ci: Cannot connect to the Docker daemon at tcp ...
For DinD to work, Try mounting the docker socket path of CI container to docker socket path of top level docker i.e. local...
Read more >Cannot Connect to a Docker Daemon - Baeldung
In this tutorial, we'll learn about the Docker daemon connectivity issue. This is a very common error that beginners encounter.
Read more >Troubleshoot Docker Engine installation
Unable to connect to the Docker daemon This error may indicate: The Docker daemon isn't running on your system. Start the daemon and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Docker is not available on MacOS runners. See https://github.com/actions/runner-images/issues/2150 for more info.
Closing as fixed