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
On WSL, if the user does not have a .ssh dir, we get a failure when connecting to a podman machine. It is probably the same for a remote connection? And it might be only WSL, but I would guess not.
Steps to reproduce the issue
Steps to reproduce the issue
On a fresh WSL install with podman 5.3.1, run podman machine init --now
Run any podman command like podman run -it --rm alpine ls
Describe the results you received
Machine "podman-machine-default" started successfully
PS C:\Users\baude> podman run -it alpine ls
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\baude.ssh\known_hosts: The system cannot find the path specified.
Describe the results you expected
Describe the results you expected
podman info output
Note: The Podman client is 5.3.1 but downloads a 5.3.0 machine image because it is WSL
PS C:\Users\baude> 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: 98.75systemPercent: 0.97userPercent: 0.28cpus: 2databaseBackend: sqlitedistribution:
distribution: fedoravariant: containerversion: "40"eventLogger: journaldfreeLocks: 2047hostname: DESKTOP-DBVSPIQidMappings:
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: 3638992896memTotal: 4101287936networkBackend: 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.18.2-1.fc40.x86_64path: /usr/bin/crunversion: |- crun version 1.18.2 commit: 00ab38af875ddd0d1a8226addda52e1de18339b5 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: 1073741824swapTotal: 1073741824uptime: 0h 17m 26.00svariant: ""plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries:
search:
- docker.iostore:
configFile: /home/user/.config/containers/storage.confcontainerStore:
number: 1paused: 0running: 0stopped: 1graphDriverName: overlaygraphOptions: {}graphRoot: /home/user/.local/share/containers/storagegraphRootAllocated: 1081101176832graphRootUsed: 887406592graphStatus:
Backing Filesystem: extfsNative Overlay Diff: "true"Supports d_type: "true"Supports shifting: "false"Supports volatile: "true"Using metacopy: "false"imageCopyTmpDir: /var/tmpimageStore:
number: 1runRoot: /run/user/1000/containerstransientStore: falsevolumePath: /home/user/.local/share/containers/storage/volumesversion:
APIVersion: 5.3.0Built: 1731456000BuiltTime: Tue Nov 12 18:00:00 2024GitCommit: ""GoVersion: go1.22.7Os: linuxOsArch: linux/amd64Version: 5.3.0
Podman in a container
No
Privileged Or Rootless
NA
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered:
Issue Description
On WSL, if the user does not have a
.ssh
dir, we get a failure when connecting to a podman machine. It is probably the same for a remote connection? And it might be only WSL, but I would guess not.Steps to reproduce the issue
Steps to reproduce the issue
podman machine init --now
podman run -it --rm alpine ls
Describe the results you received
Machine "podman-machine-default" started successfully
PS C:\Users\baude> podman run -it alpine ls
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\baude.ssh\known_hosts: The system cannot find the path specified.
Describe the results you expected
Describe the results you expected
podman info output
Note: The Podman client is 5.3.1 but downloads a 5.3.0 machine image because it is WSL
Podman in a container
No
Privileged Or Rootless
NA
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: