Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error connecting to Docker daemon on macOS with Docker Desktop 4.13
See original GitHub issueWhen using Docker Desktop 4.13, the Maven spring-boot:build-image goal and Gradle bootBuildImage task might fail with an error message like this:
Connection to the Docker daemon at 'localhost' failed with error "[2] No such file or directory"; ensure the Docker daemon is running and accessible
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Docker 4.13.0 does not start up on macOS Ventura #6547
After attempting to start Docker Desktop for macOS Ventura, ... Cannot connect to the Docker daemon at unix://docker.raw.sock.
Read more >Cannot connect to the Docker daemon on macOS
On a supported Mac, run: brew install --cask docker. Then launch the Docker app. Click next. It will ask for privileged access. Confirm....
Read more >Known issues for Docker Desktop on Mac
Docker does not auto-start on login even when it is enabled in Preferences. This is related to a set of issues with Docker...
Read more >How to Resolve the “cannot connect to the Docker daemon ...
The “cannot connect to the Docker daemon” error in Docker usually happens when running the docker-compose build command.
Read more >GitLab runner 15.5.0 macOS Silicon unable to connect to the ...
I am trying to set up GitLab runner 15.5.0 on Apple Silicon with docker, so I can run the jobs in containers. The...
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 Free
Top 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
They’re going to roll the change back to give folks more time to adapt: https://github.com/docker/for-mac/issues/6529#issuecomment-1292135881
@philwebb Looks like the latest build fixes it, now unix:///Users/USER/.docker/run/docker.sock is getting created again, but a new issue has shown up. Looks like -f was removed from the docker command so now IntelliJ doesn’t work anymore. Nice. It gets the error “unknown shorthand flag: ‘f’ in -f” changing IntelliJ not to use Compose V2 works, but not ideal.