After installing and running podman, there is no alias for docker client

[maxandersen]

Bug description

installed podman desktop. it says it is running but running docker ps I get:

docker ps
Cannot connect to the Docker daemon at unix:///Users/manderse/.docker/run/docker.sock. Is the docker daemon running?

note I installed docker desktop the other day so maybe some mismatches here?

Sub-tasks:

• docker system helper / podman-mac-helper installation should be setup by default on macOS containers/podman#16547
• docker socket helper should also setup local socket path on macOS containers/podman#16548
• Provide settings to show if Docker compatibility mode is active or not #905

Operating system

macos monterey - apple M1 Max

Version

0.9.0

Steps to reproduce

No response

Relevant log output

No response

Additional context

No response

[maxandersen]

also testcontainers can't detect any running docker compatible container:

2022-11-03 09:14:55,052 WARN  [io.qua.dat.dep.dev.DevServicesDatasourceProcessor] (build-40) Unable to determine a database type for default datasource
2022-11-03 09:14:55,085 WARN  [org.tes.uti.TestcontainersConfiguration] (build-40) Attempted to read Testcontainers configuration file at file:/Users/manderse/.testcontainers.properties but the file was not found. Exception message: FileNotFoundException: /Users/manderse/.testcontainers.properties (No such file or directory)
2022-11-03 09:14:55,185 WARN  [org.tes.doc.DockerClientProviderStrategy] (build-40) DOCKER_HOST unix:///var/run/docker.sock is not listening
2022-11-03 09:14:55,187 INFO  [org.tes.doc.DockerMachineClientProviderStrategy] (build-40) docker-machine executable was not found on PATH ([/Users/manderse/.jbang/cache/jdks/17/bin, /Users/manderse/.jbang/bin, /Users/manderse/.yarn/bin, /Users/manderse/.config/yarn/global/node_modules/.bin, /Users/max/.local/bin, ~/.krew/bin, /Users/manderse/bin, /opt/homebrew/bin, /opt/homebrew/sbin, /usr/local/bin, /System/Cryptexes/App/usr/bin, /usr/bin, /bin, /usr/sbin, /sbin, /usr/local/munki, /Users/manderse/.rvm/bin])
2022-11-03 09:14:55,187 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-40) Could not find a valid Docker environment. Please check configuration. Attempted configurations were:
2022-11-03 09:14:55,187 ERROR [org.tes.doc.DockerClientProviderStrategy] (build-40) As no valid configuration was found, execution cannot continue

[slemeur]

At the moment we are not mapping the docker socket (or host) to podman automatically.
We thought not all users would want to get that automated and were thinking to enable this option as part of the onboarding sequence and from the settings.

[maxandersen]

Which users would NOT want this? I would argue a minor portion of users as without it the majority of the existing container ecosystem tooling just doesn't work.

yes, make it part of onboarding but please make it default on so we don't have to give multistep guides to developers on how to configure podman to work with existing container tooling :)

[benoitf]

the default is performed by Podman side (the podman machine) so probably we should move the issue to podman repository.

Machine default is reporting:

The system helper service is not installed; the default Docker API socket
address can't be used by podman. If you would like to install it run the
following command:

	sudo /opt/homebrew/Cellar/podman/4.3.0/bin/podman-mac-helper install

[benoitf]

We could exposed the installation on the UI but it would still not be the default until it's defaulted on podman machine side.

[benoitf]

created containers/podman#16547 and containers/podman#16548

[n1hility]

Brew based installs of podman can't do this by default, package installation is purposefully not ran as root, and packages are supposed to indicate root actions as a separate step. So the best we could do is after a brew install is print directions.

In the Mac installer case, we can do this properly, although currently, podman desktop supports both brew and non-brew.

IMO the only workable solution is if podman-desktop checks this and prompts to enable the podman-mac-helper service