When start podman machine : "ssh error: machine not in running state"

### Issue Description

I've come from Docker Desktop and Rancher Desktop, which both worked well.
I've had nothing but problems with Podman though.
Podman desktop cannot start a podman machine
When running "podman --log-level=trace machine start", i get the following output

`time="2025-08-22T14:42:39+02:00" level=info msg="C:\\Program Files\\RedHat\\Podman\\podman.exe filtering at log level trace"
time="2025-08-22T14:42:39+02:00" level=debug msg="Using Podman machine with `wsl` virtualization provider"
time="2025-08-22T14:42:39+02:00" level=debug msg="socket length for C:\\Users\\lchorley\\.config\\containers\\podman\\machine\\wsl is 55"
time="2025-08-22T14:42:39+02:00" level=debug msg="socket length for C:\\Users\\lchorley\\.local\\share\\containers\\podman\\machine\\wsl is 60"
time="2025-08-22T14:42:39+02:00" level=debug msg="socket length for C:\\Users\\lchorley\\.local\\share\\containers\\podman\\machine\\wsl\\cache is 66"
time="2025-08-22T14:42:39+02:00" level=debug msg="socket length for C:\\Users\\lchorley\\AppData\\Local\\Temp\\podman is 43"
time="2025-08-22T14:42:39+02:00" level=debug msg="socket length for C:\\Users\\lchorley\\.config\\containers\\podman\\machine\\wsl\\podman-machine-default.json is 83"
Starting machine "podman-machine-default"
time="2025-08-22T14:42:39+02:00" level=debug msg="writing configuration file \"C:\\\\Users\\\\lchorley\\\\.config\\\\containers\\\\podman\\\\machine\\\\wsl\\\\podman-machine-default.json\""
time="2025-08-22T14:42:39+02:00" level=debug msg="socket length for C:\\Users\\lchorley\\AppData\\Local\\Temp\\podman\\gvproxy.pid is 55"
time="2025-08-22T14:42:39+02:00" level=debug msg="Running command: C:\\windows\\system32\\wsl.exe [wsl -u root -d podman-machine-default /root/bootstrap]"

This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:

        podman machine set --rootful

time="2025-08-22T14:42:43+02:00" level=debug msg="socket length for C:\\Users\\lchorley\\AppData\\Local\\Temp\\podman\\podman-machine-default-api.sock is 75"
API forwarding for Docker API clients is not available due to the following startup failures.
        could not start api proxy since expected pipe is not available: podman-machine-default

Podman clients are still able to connect.
time="2025-08-22T14:43:04+02:00" level=debug msg="writing configuration file \"C:\\\\Users\\\\lchorley\\\\.config\\\\containers\\\\podman\\\\machine\\\\wsl\\\\podman-machine-default.json\""
Error: machine did not transition into running state: ssh error: machine not in running state
time="2025-08-22T14:43:04+02:00" level=debug msg="Shutting down engines"`

I've tried using the images 5.1-rootfs-amd64.tar.zst and 5.3-rootfs-amd64.tar.zst as suggested here : https://github.com/containers/podman/issues/22240
But no improvement

Does anyone have any ideas ?
Thank you !

Extra info



### Steps to reproduce the issue

Steps to reproduce the issue
1. install podman
2. run podman machine init
3. run podman machine start


### Describe the results you received

API forwarding for Docker API clients is not available due to the following startup failures.
        could not start api proxy since expected pipe is not available: podman-machine-default

and 

Error: machine did not transition into running state: ssh error: machine not in running state


### Describe the results you expected

That the machine starts without any problems

### podman info output

```yaml
I'm running windows 10 Version 10.0.19043 Build 19043


podman version
Client:       Podman Engine
Version:      5.6.0
API Version:  5.6.0
Go Version:   go1.25.0
Git Commit:   da671ef6cfa3fc9ac6225c18f1dd0a70a951e43f
Built:        Fri Aug 15 17:45:10 2025
OS/Arch:      windows/amd64

Server:       Podman Engine
Version:      5.3.1
API Version:  5.3.1
Go Version:   go1.22.7
Built:        Thu Nov 21 01:00:00 2024
OS/Arch:      linux/amd64

podman info
Client:
  APIVersion: 5.6.0
  Built: 1755272710
  BuiltTime: Fri Aug 15 17:45:10 2025
  GitCommit: da671ef6cfa3fc9ac6225c18f1dd0a70a951e43f
  GoVersion: go1.25.0
  Os: windows
  OsArch: windows/amd64
  Version: 5.6.0
host:
  arch: amd64
  buildahVersion: 1.38.0
  cgroupControllers: []
  cgroupManager: cgroupfs
  cgroupVersion: v1
  conmon:
    package: conmon-2.1.12-2.fc40.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.12, commit: '
  cpuUtilization:
    idlePercent: 99.76
    systemPercent: 0.12
    userPercent: 0.12
  cpus: 4
  databaseBackend: sqlite
  distribution:
    distribution: fedora
    variant: container
    version: "40"
  eventLogger: journald
  freeLocks: 2048
  hostname: LCHORLEY21-LA
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 524288
      size: 65536
  kernel: 5.10.102.1-microsoft-standard-WSL2
  linkmode: dynamic
  logDriver: journald
  memFree: 3858030592
  memTotal: 4114530304
  networkBackend: netavark
  networkBackendInfo:
    backend: netavark
    dns:
      package: aardvark-dns-1.13.1-1.fc40.x86_64
      path: /usr/libexec/podman/aardvark-dns
      version: aardvark-dns 1.13.1
    package: netavark-1.13.1-1.fc40.x86_64
    path: /usr/libexec/podman/netavark
    version: netavark 1.13.1
  ociRuntime:
    name: crun
    package: crun-1.19.1-1.fc40.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.19.1
      commit: 3e32a70c93f5aa5fea69b50256cca7fd4aa23c80
      rundir: /run/user/1000/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
  os: linux
  pasta:
    executable: /usr/bin/pasta
    package: passt-0^20250121.g4f2c8e7-2.fc40.x86_64
    version: |
      pasta 0^20250121.g4f2c8e7-2.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: true
    path: unix:///run/user/1000/podman/podman.sock
  rootlessNetworkCmd: pasta
  security:
    apparmorEnabled: false
    capabilities: 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_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: true
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 1073741824
  swapTotal: 1073741824
  uptime: 0h 9m 7.00s
  variant: ""
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries:
  search:
  - docker.io
store:
  configFile: /home/user/.config/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /home/user/.local/share/containers/storage
  graphRootAllocated: 269490393088
  graphRootUsed: 984305664
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Supports shifting: "true"
    Supports volatile: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 0
  runRoot: /run/user/1000/containers
  transientStore: false
  volumePath: /home/user/.local/share/containers/storage/volumes
version:
  APIVersion: 5.3.1
  Built: 1732147200
  BuiltTime: Thu Nov 21 01:00:00 2024
  GitCommit: ""
  GoVersion: go1.22.7
  Os: linux
  OsArch: linux/amd64
  Version: 5.3.1
```

### Podman in a container

No

### Privileged Or Rootless

Rootless

### 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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

When start podman machine : "ssh error: machine not in running state" #26888

Issue Description

Steps to reproduce the issue

Describe the results you received

Describe the results you expected

podman info output

Podman in a container

Privileged Or Rootless

Upstream Latest Release

Additional environment details

Additional information

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

When start podman machine : "ssh error: machine not in running state" #26888

Description

Issue Description

Steps to reproduce the issue

Describe the results you received

Describe the results you expected

podman info output

Podman in a container

Privileged Or Rootless

Upstream Latest Release

Additional environment details

Additional information

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions