You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Podman 5.3.0 on Windows throws exception on missing path when run.
Steps to reproduce the issue
Steps to reproduce the issue
In my case I had 5.2.5 installed via winget (pretty vanilla install) and upgraded using winget upgrade --all
the podman machine would start, but when trying issue a podman ps -a and other commands I would get a connectivity error
logging into the machine allowed podman ps -a to work fine
I uninstalled the machine and podman and then reinstalled 5.3.0 directly, but faced the same issue
Describe the results you received
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 socket: open C:\Users{username}.ssh\known_hosts: The system cannot find the path specified.
Describe the results you expected
I expected to see the containers on the machine
podman info output
PS C:\Users\scott> podman versionClient: Podman EngineVersion: 5.3.0API Version: 5.3.0Go Version: go1.23.3Git Commit: 874bf2c301ecf0ba645f1bb45f81966cc755b7daBuilt: Wed Nov 13 08:19:59 2024OS/Arch: windows/amd64Server: Podman EngineVersion: 5.3.0API Version: 5.3.0Go Version: go1.22.7Built: Tue Nov 12 19:00:00 2024OS/Arch: linux/amd64PS C:\Users\scott> podman infohost:
arch: amd64buildahVersion: 1.38.0cgroupControllers: []cgroupManager: cgroupfscgroupVersion: v1conmon:
package: conmon-2.1.12-2.fc40.x86_64path: /usr/bin/conmonversion: 'conmon version 2.1.12, commit: 'cpuUtilization:
idlePercent: 99.1systemPercent: 0.35userPercent: 0.55cpus: 12databaseBackend: sqlitedistribution:
distribution: fedoravariant: containerversion: "40"eventLogger: journaldfreeLocks: 2041hostname: SPRUDY-SP9idMappings:
gidmap:
- container_id: 0host_id: 1000size: 1
- container_id: 1host_id: 524288size: 65536uidmap:
- container_id: 0host_id: 1000size: 1
- container_id: 1host_id: 524288size: 65536kernel: 5.15.167.4-microsoft-standard-WSL2linkmode: dynamiclogDriver: journaldmemFree: 6386536448memTotal: 8238841856networkBackend: netavarknetworkBackendInfo:
backend: netavarkdns:
package: aardvark-dns-1.12.2-2.fc40.x86_64path: /usr/libexec/podman/aardvark-dnsversion: aardvark-dns 1.12.2package: netavark-1.12.2-1.fc40.x86_64path: /usr/libexec/podman/netavarkversion: netavark 1.12.2ociRuntime:
name: crunpackage: crun-1.17-1.fc40.x86_64path: /usr/bin/crunversion: |- crun version 1.17 commit: 000fa0d4eeed8938301f3bcf8206405315bc1017 rundir: /run/user/1000/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt-0^20241030.gee7d0b6-1.fc40.x86_64version: | pasta 0^20241030.gee7d0b6-1.fc40.x86_64 Copyright Red Hat GNU General Public License, version 2 or later <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.remoteSocket:
exists: truepath: unix:///run/user/1000/podman/podman.sockrootlessNetworkCmd: pastasecurity:
apparmorEnabled: falsecapabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOTrootless: trueseccompEnabled: trueseccompProfilePath: /usr/share/containers/seccomp.jsonselinuxEnabled: falseserviceIsRemote: trueslirp4netns:
executable: ""package: ""version: ""swapFree: 2147483648swapTotal: 2147483648uptime: 0h 10m 55.00svariant: ""plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries:
search:
- docker.iostore:
configFile: /home/user/.config/containers/storage.confcontainerStore:
number: 5paused: 0running: 4stopped: 1graphDriverName: overlaygraphOptions: {}graphRoot: /home/user/.local/share/containers/storagegraphRootAllocated: 1081101176832graphRootUsed: 1758658560graphStatus:
Backing Filesystem: extfsNative Overlay Diff: "true"Supports d_type: "true"Supports shifting: "false"Supports volatile: "true"Using metacopy: "false"imageCopyTmpDir: /var/tmpimageStore:
number: 4runRoot: /run/user/1000/containerstransientStore: falsevolumePath: /home/user/.local/share/containers/storage/volumesversion:
APIVersion: 5.3.0Built: 1731456000BuiltTime: Tue Nov 12 19:00:00 2024GitCommit: ""GoVersion: go1.22.7Os: linuxOsArch: linux/amd64Version: 5.3.0
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
PS C:\Users\scott> cmd /c ver
Microsoft Windows [Version 10.0.22631.4460]
PS C:\Users\scott> wsl -l -v
NAME STATE VERSION
I was able to eventually workaround the issue by adding an empty C:\Users\{username}\.ssh\known_hosts file, but given that the file is 0 bytes, it doesn't seem like it's something the podman command should fail on or at least possibly the installer could touch the file to ensure it exists.
The text was updated successfully, but these errors were encountered:
Issue Description
Podman 5.3.0 on Windows throws exception on missing path when run.
Steps to reproduce the issue
Steps to reproduce the issue
podman ps -a
and other commands I would get a connectivity errorpodman ps -a
to work fineDescribe the results you received
Cannot connect to Podman. Please verify your connection to the Linux system using
podman system connection list
, or trypodman machine init
andpodman machine start
to manage a new Linux VMError: unable to connect to Podman socket: open C:\Users{username}.ssh\known_hosts: The system cannot find the path specified.
Describe the results you expected
I expected to see the containers on the machine
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
PS C:\Users\scott> cmd /c ver
Microsoft Windows [Version 10.0.22631.4460]
PS C:\Users\scott> wsl -l -v
NAME STATE VERSION
podman-machine-default Running 2
PS C:\Users\scott> wsl --version
WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4460
Additional information
I was able to eventually workaround the issue by adding an empty
C:\Users\{username}\.ssh\known_hosts
file, but given that the file is 0 bytes, it doesn't seem like it's something the podman command should fail on or at least possibly the installer could touch the file to ensure it exists.The text was updated successfully, but these errors were encountered: