Missing specific Podman named pipe on Windows if DockerDesktop engine is not installed #13502
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
windows
issue/bug on Windows
/kind feature
Description
When a podman machine starts on Windows, it checks if there is DockerDesktop or not and then if Docker Desktop is not there it will create the named pipe
//./pipe/docker_engine
But if Docker Desktop engine is there, it will register the named pipe
//./pipe/podman-<name-of-the-machine>
The problem is that the 'Docker emulation mode' should not prevent the specific podman channel to be created.
For example if I may want to always use the 'podman' channel to discuss on its own REST API.
Describe the results you received:
Podman named pipe is either
//./pipe/podman-<name-of-the-machine>
or//./pipe/docker_engine
depending of if DockerDesktop is there or not.Describe the results you expected:
Podman named pipe
//./pipe/podman-<name-of-the-machine>
should always be there (no matter if DockerDesktop is there or not)Additional information you deem important (e.g. issue happens only occasionally):
I checked the named pipe available using on PowerShell the command
[System.IO.Directory]::GetFiles("\\.\\pipe\\")
podman/pkg/machine/wsl/machine.go
Lines 805 to 811 in f918a94
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: