Docker Socket Compatibility: Docker-specific tools may not work.

[bathivinod]

While I am starting Podman on Windows, we are getting below error

Docker Socket Compatibility: Docker-specific tools may not work.

I have added below environment variable also
C:\Users\VINOD\.local\share\containers\podman-desktop\extensions-storage\podman-desktop.compose\bin

[mairin]

@bathivinod we're redesigning the UI for this (check out the Design category in this forum.) It's not really an error... it's just letting you know Podman isn't connected to the Docker socket.

[bathivinod]

If Podman isn't connected to the Docker socket means that is also an issue, how to resolve

[benoitf]

It means that if you have tools like IDE plugins l, 3rd party tools that connect to barcoded /var/run/docker.sock path it won't work

On windows/macOS there are helpers with 'podman machines command

On Linux you can do a symlink from your podman socket to /var/run/docker.sock but then you could have permissions issues or grant too many permissions.

It depends if you have 3rd party tools

[bathivinod]

Ok I understand, Thank you
Where can we find logs for Podman Desktop in Windows

[afbjorklund]

The warning looks extra weird, when you get it next to the running Docker...

Like on Ubuntu:

The reason that it doesn't work for Podman, is that it is already running Docker.

But that's different from saying "Docker-specific tools may not work" (for Podman!)
Or that the "Docker socket is not reachable", just because it doesn't understand libpod.

Normally we would prefer to set DOCKER_HOST (or the docker context), to the right one ?

[mairin]

@afbjorklund Yehhhh - I'm working on mockups for updating our approach to docker compat in podman this past sprint and this sprint too. Essentially that warning is going to go away and be replaced with something less error message-y, and we'll have a docker compatibility settings page for podman under settings that will hopefully make it less weird. I'm going to post to the discussion board here soon.