docs: Correct windows instructions for migrating from docker

[foxydevloper]

What does this PR do?

On windows, DOCKER_HOST is set to a named pipe instead of a socket, and podman has a seperate field for it, "PodmanPipe", the docs accidentally put "PodmanSocket" on windows. This also notes that you don't actually need to set DOCKER_HOST on windows, since podman already uses the default docker_engine named pipe.

How to test this PR?

Run command on windows

[cdrage]

You're completely correct, this should of been npipe:// I even see it's the same in the docker documentation as well: https://docs.docker.com/desktop/faqs/general/

Thanks for this contribution!

[foxydevloper]

Fixed the build. Here's how the built docs look:

[ReadingShades]

Well, first of all, @foxydevloper thank you. I ran into this issue yesterday while installing podman for the first time in my Windows machine and finally solved it today with your aid.

On the other hand, I also suggest adding a note about command line emulators:

The export command to set environment variables only works io Git Bash in windows.

Mostly to clean it up for clarity/newbies (like me):

Windows socket manual configuration:

Command to get socket path config:

podman machine inspect --format '{{.ConnectionInfo.PodmanPipe.Path}}'

Changing all the backwards slashes for forward slashes.
Itshould look like:

//./pipe/podman-machine-default

To this path you must then add the prefix:

npipe://

The final path should look like

npipe:////./pipe/podman-machine-default

Commands to set the environment variable:

cmd:

set DOCKER_HOST=npipe://<inspect_command_output>

example:

set DOCKER_HOST=npipe:////./pipe/podman-machine-default

Git Bash:

export DOCKER_HOST=npipe://<inspect_command_output>

example:

export DOCKER_HOST=npipe:////./pipe/podman-machine-default

powershell:

$env:DOCKER_HOST="npipe://<inspect_command_output>"

note: Don't miss the quotes on the value or powershell will try to interpret it as a command.

example:

$env:DOCKER_HOST="npipe:////./pipe/podman-machine-default"

[foxydevloper]

On windows you can also set the environment variable in the windows environment variables program. But yeah, I kind of missed that part. If you're able to make a PR with those changes you could definitely go for it!

[ReadingShades]

On windows you can also set the environment variable in the windows environment variables program. But yeah, I kind of missed that part. If you're able to make a PR with those changes you could definitely go for it!

Hmm sure, why not? IT is Hacktoberfest and a good chance as any to make a contribution.