Issue Description
Installing Podman and creating the default machine WITH user mode networking enabled leads to commands that need dns resolution not working such as but not limited to podman compose up --build.
Steps to reproduce the issue
Steps to reproduce the issue
-1. set wsl to mirrored mode.
0. delete podman and "unregister" old podman distros if you had podman installed and running already.
- install podman.
- go through the initial setup.
- go to resources and create a podman machine WITH user mode networking enabled.
- after podman toasts that it is done open windows terminal and podman-machine-default and podman-net-usermode distros should be created.
- connect to a vpn.
- attach to podman-machine-default:
[user@computer~]$ ping google.com
^C --> not working
[user@computer~]$ cat /etc/resolv.conf
nameserver 192.168.127.1
[user@computer~]$ ls -l /etc/resolv.conf
--> not a symlink
[user@computer~]$ cat /etc/wsl.conf
[user]
default=user
[network]
generateResolvConf = false
Describe the results you received
Two distros were created:
podman-machine-default
-> can not resolve dns when host is connected to vpn.
podman-net-usermode
-> can resolve dns when host is connected to vpn.
BUT:
podman-net-usermode is apparently not used.
Describe the results you expected
That podman actually uses the second working distro somehow OR
That only podman-machine-default is created but with a generated resolv.conf (this works on all other wsl distros and does not break when the host is connected to a vpn).
podman info output
Client:
APIVersion: 5.8.1
Built: 1773259081
BuiltTime: Wed Mar 11 20:58:01 2026
GitCommit: c6077f645788743258a1a749f8005b4fb3cbe533
GoVersion: go1.26.1
Os: windows
OsArch: windows/amd64
Version: 5.8.1
host:
arch: amd64
buildahVersion: 1.43.0
cgroupControllers:
- cpuset
- cpu
- io
- memory
- hugetlb
- pids
- rdma
cgroupManager: cgroupfs
cgroupVersion: v2
conmon:
package: conmon-2.2.1-2.fc43.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.2.1, commit: '
cpuUtilization:
idlePercent: 99.63
systemPercent: 0.22
userPercent: 0.15
cpus: 20
databaseBackend: sqlite
distribution:
distribution: fedora
variant: container
version: "43"
eventLogger: journald
freeLocks: 2048
hostname: CEPF4DKY46
idMappings:
gidmap: null
uidmap: null
kernel: 6.6.87.2-microsoft-standard-WSL2
linkmode: dynamic
logDriver: journald
memFree: 15393984512
memTotal: 16623239168
networkBackend: netavark
networkBackendInfo:
backend: netavark
defaultNetwork: podman
dns:
package: aardvark-dns-1.17.0-1.fc43.x86_64
path: /usr/libexec/podman/aardvark-dns
version: aardvark-dns 1.17.0
package: netavark-1.17.2-1.fc43.x86_64
path: /usr/libexec/podman/netavark
version: netavark 1.17.2
ociRuntime:
name: crun
package: crun-1.25.1-1.fc43.x86_64
path: /usr/bin/crun
version: |-
crun version 1.25.1
commit: 156ae065d4a322d149c7307034f98d9637aa92a2
rundir: /run/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^20260120.g386b5f5-1.fc43.x86_64
version: |
pasta 0^20260120.g386b5f5-1.fc43.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/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: false
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: false
serviceIsRemote: true
slirp4netns:
executable: ""
package: ""
version: ""
swapFree: 4294967296
swapTotal: 4294967296
uptime: 0h 28m 22.00s
variant: ""
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
- ipvlan
volume:
- local
registries:
search:
- docker.io
store:
configFile: /usr/share/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.additionalImageStores:
- /usr/lib/containers/storage
overlay.imagestore: /usr/lib/containers/storage
overlay.mountopt: nodev,metacopy=on
graphRoot: /var/lib/containers/storage
graphRootAllocated: 1081101176832
graphRootUsed: 898977792
graphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Supports shifting: "true"
Supports volatile: "true"
Using metacopy: "true"
imageCopyTmpDir: /var/tmp
imageStore:
number: 0
runRoot: /run/containers/storage
transientStore: false
volumePath: /var/lib/containers/storage/volumes
version:
APIVersion: 5.8.1
BuildOrigin: 'Copr: packit/containers-podman-28250'
Built: 1773187200
BuiltTime: Wed Mar 11 01:00:00 2026
GitCommit: c6077f645788743258a1a749f8005b4fb3cbe533
GoVersion: go1.25.7 X:nodwarf5
Os: linux
OsArch: linux/amd64
Version: 5.8.1Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
WSL is in mirrored mode.
Additional information
I can fix the setup by setting generateResolvConf = true, removing /etc/resolv.conf and restarting the wsl.
But what is the point about giving me a setting when it does not work? And what is the point of the podman-net-usermode WSL distro if I have to reconfigure podman-machine-default to make it work?
Issue Description
Installing Podman and creating the default machine WITH user mode networking enabled leads to commands that need dns resolution not working such as but not limited to podman compose up --build.
Steps to reproduce the issue
Steps to reproduce the issue
-1. set wsl to mirrored mode.
0. delete podman and "unregister" old podman distros if you had podman installed and running already.
Describe the results you received
Two distros were created:
podman-machine-default
-> can not resolve dns when host is connected to vpn.
podman-net-usermode
-> can resolve dns when host is connected to vpn.
BUT:
podman-net-usermode is apparently not used.
Describe the results you expected
That podman actually uses the second working distro somehow OR
That only podman-machine-default is created but with a generated resolv.conf (this works on all other wsl distros and does not break when the host is connected to a vpn).
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
WSL is in mirrored mode.
Additional information
I can fix the setup by setting
generateResolvConf = true, removing/etc/resolv.confand restarting the wsl.But what is the point about giving me a setting when it does not work? And what is the point of the podman-net-usermode WSL distro if I have to reconfigure podman-machine-default to make it work?