Skip to content
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

Open
ThomasVitale opened this issue May 25, 2023 · 6 comments
Open

Docker compatibility on macOS doesn't work anymore #2630

ThomasVitale opened this issue May 25, 2023 · 6 comments

Comments

@ThomasVitale
Copy link

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

@benoitf
Copy link
Collaborator

benoitf commented May 25, 2023

hello, for now you can switch the docker context to use the global location

docker context use default (or select the /var/run/docker.sock from docker context ls)

you could comment the issue on Podman as well containers/podman#16548 as it's still not binding the local socket

@ThomasVitale
Copy link
Author

@benoitf thank you so much for your reply. Changing the Docker context worked.

@vyasgun
Copy link
Contributor

vyasgun commented May 31, 2023

/assign

@vyasgun vyasgun self-assigned this Jun 1, 2023
@vyasgun vyasgun moved this from 📋 Backlog to 🚧 In Progress in Podman Desktop Planning Jun 22, 2023
@vyasgun vyasgun moved this from 🚧 In Progress to 🚥 In Review in Podman Desktop Planning Jun 29, 2023
@nichjones1 nichjones1 assigned jeffmaury and unassigned vyasgun Sep 27, 2023
@benoitf
Copy link
Collaborator

benoitf commented Sep 27, 2023

I think podman machine, should register a docker context 'podman' and switch to this context if the current context is not reachable

@jeffmaury jeffmaury moved this from 🚥 In Review to 📅 Planned in Podman Desktop Planning Sep 29, 2023
@nichjones1 nichjones1 moved this from 📅 Planned to 🚧 In Progress in Podman Desktop Planning Oct 3, 2023
jeffmaury added a commit to jeffmaury/podman-desktop that referenced this issue Oct 5, 2023
@jeffmaury jeffmaury moved this from 🚧 In Progress to 🚥 In Review in Podman Desktop Planning Oct 5, 2023
@nichjones1 nichjones1 added this to the 1.6.0 milestone Nov 9, 2023
@benoitf benoitf removed this from the 1.6.0 milestone Dec 6, 2023
@nichjones1 nichjones1 moved this from 🚥 In Review to ⏱Postponed in Podman Desktop Planning Feb 20, 2024
Copy link
Contributor

github-actions bot commented Jun 4, 2024

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!

@jeffmaury
Copy link
Contributor

PR attached

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants