Unable to complete podman machine init on Windows 10 WSL 2

[JerryMWeeks]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

podman machine init fails at resolving hostname mirrors.fedoraproject.org
Annoying manual clean up of .config, .default, and appdata/roaming/containers/containers.conf if you want to try rerunning, and ."file already in use error follows failure when init is rerun (seperate issue to this one)_

Steps to reproduce the issue:

1. remove all WSL / Windows features for virtualization - reboot etc.
2. Run elevated PowerShell 7
3. Run WSL --install - wait, reboot etc
4. Check new Ubuntu auto runs
5. run elevated PowerShell 7 and run command wsl --set-default-version 2
6. Download latest (4.1.1) Windows msi from Podman releases
7. Reboot if required etc.
8. run elevated PowerShell 7 and run command podman machine init

The output is below

Describe the results you received:

podman machine init
Downloading VM image: fedora-35-x86_64.tar.xz: done
Extracting compressed file
Importing operating system into WSL (this may take 5+ minutes on a new WSL install)...
Installing packages (this will take awhile)...
Failed to set locale, defaulting to C.UTF-8
Fedora 35 - x86_64                                                                      0.0  B/s |   0  B     02:00
Errors during downloading metadata for repository 'fedora':
 - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64&countme=1 [Could not resolve host: mirrors.fedoraproject.org]
 - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]
Error: package upgrade on guest OS failed: exit status 1

Describe the results you expected:

As described in Run Podman Windows RedHat Tom Sweeney

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

podman version
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: failed to parse identity "C:\\Users\\jerry\\.ssh\\podman-machine-default": open C:\Users\jerry\.ssh\podman-machine-default: The system cannot find the file specified.
PS C:\Windows\System32>

or

podman --version
podman version 4.1.1

Output of podman info --debug:

podman info --debug
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: failed to parse identity "C:\\Users\\jerry\\.ssh\\podman-machine-default": open C:\Users\jerry\.ssh\podman-machine-default: The system cannot find the file specified.
PS C:\Windows\System32>

Package info (e.g. output of rpm -q podman or apt list podman):

none /not possible

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.):
Windows 10

ver
Microsoft Windows [Version 10.0.19044.1706]

[JerryMWeeks]

How do I try out this (as an experiment)
podman run --security-opt seccomp=/path/to/default.json
As described here: Bug#995777

[JerryMWeeks]

Possible duplicate of #14495

[Luap99]

lets close this as duplicate of #14495 to keep the discussion in one place

[JerryMWeeks]

Not quite a duplicate as #14495 is DNS resolution and this is ability to actually init a podman default.
But since all my comments are over on 14495 lets leave it at that! 👍