-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker compatibility on macOS doesn't work anymore #2630
Comments
hello, for now you can switch the docker context to use the global location
you could comment the issue on Podman as well containers/podman#16548 as it's still not binding the local socket |
@benoitf thank you so much for your reply. Changing the Docker context worked. |
/assign |
I think podman machine, should register a docker context 'podman' and switch to this context if the current context is not reachable |
Fixes podman-desktop#2630 Signed-off-by: Jeff MAURY <[email protected]>
This issue has been automatically marked as stale because it has not had activity in the last 6 months. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions! |
PR attached |
Bug description
Before upgrading to newer versions of Docker Desktop and Podman Desktop, the Docker compatibility layer on my MacBook was working correctly (macOS Ventura on M1). I'm currently using Docker Desktop 4.19.0 and Podman Desktop 1.0.1, and I can't run Docker commands anymore.
From what I understood, recent versions of Docker Desktop moved the default socket location from
/var/run/docker.sock
to/Users/<username>/.docker/run/docker.sock
, and a link exists from the first to the second.The result is that whenever I type Docker commands to interact with Podman transparently (e.g.
docker ps
), the command fails with the following error because Podman Desktop knows how to intercept the first socket location and not the second one.Cannot connect to the Docker daemon at unix:///Users/<user>/.docker/run/docker.sock. Is the docker daemon running?
I found a solution for Linux in #2388 (comment), but I didn't find a way to make it work on macOS. Do you have any suggestion?
Operating system
macOS Ventura 13.3.1 (M1)
Version
1.0.x
Steps to reproduce
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: