Podman 4.0.3 on Windows Named Pipe Issue

[theonewolf]

My podman defaults to setting up a docker_engine Named Pipe on Windows, not a machine-based Named Pipe.

Podman is resolving this, but it is not released yet: containers/podman#13655

It would be nice if we could specify the Named Pipe to connect to.

[iongion]

Hi @theonewolf - thanks for the report, I am planing a re-architecture of all connection management, evaluating

• connect using a custom string
• connect using remote connections
• simultaneous combined connections
• consume the familiar API for as long as libpod will follow it

[iongion]

What do you think 😸

[iongion]

Just released in 4.0.3-rc5 https://github.com/iongion/podman-desktop-companion/releases/tag/4.0.3-rc.5

[theonewolf]

@iongion it WORKS!

I was able to connect to my podman API on Windows by customizing the NamedPipe path.

Now I think it's incorrectly reporting my machine as not running, but I can live with that :-)