'What could be the reason why Podman isn't working on Remote Containers?

Any tips on why Remote - Containers isn't working?

  • Installed podman v4.1.0 on Windows 11 via .msi package
  • Ran podman machine init
  • Ran podman machine start
  • Everything is working with podman

But Remote - Containers on VSCode doesn't recognize podman.

Image: Not working. Why?

VSCode Logs as follows...

[2022-05-19T09:39:32.232Z] Start: Run: podman version --format {{.Server.APIVersion}}
[2022-05-19T09:39:32.390Z] Stop (158 ms): Run: podman version --format {{.Server.APIVersion}}
[2022-05-19T09:39:32.391Z] Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman. failed to create sshClient: dial unix \\.\pipe\openssh-ssh-agent: connect: No connection could be made because the target machine actively refused it.

Side Note: Docker extension (ms-azuretools.vscode-docker) with Docker Path set to podman is working fine.

visual-studio-codepodmanpythonpowershellterminaldirectory


Solution 1:[1]

Please confirm you are running the latest build (prerelease)

v0.236.1.

(there are known issues on github with earlier release, fixed in this version)

Solution 2:[2]

in a WSL shell, i.e. for debugging try this

first - try to start podman podlib REST api (for socket, lifetime 5000 sec. - set to zero for "forever")

podman system service -t 5000 &

then symlink the podman.sock to the location vscode expects:

sudo ln -s /mnt/wslg/runtime-dir/podman/podman.sock /var/run/docker.sock

if none of that works, would you mind posting a dump:

podman info

HINT: check the podman info YAML output for host | remoteSocket | path & make sure it matches the path /mnt/wslg/runtime-dir/podman/podman.sock above.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Brian Horakh
Solution 2 Brian Horakh

Related Questions