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
Krzysztof318 opened this issue
Jan 21, 2025
· 1 comment
Labels
kind/bugCategorizes issue or PR as related to a bug.networkNetworking related issue or featureremoteProblem is in podman-remotewindowsissue/bug on Windows
I have a problem with rootful podman, when I create container on default bridge network I can't access the internet, it is not a dns issue, because I can't even ping ip addresses like 8.8.8.8. Only solution is creating container with --network host then internet access works.
When I login manually to machine wsl -d podman-machine-default everything work correctly.
This problem doesn't occur on rootless podman, then containers on bridge network have internet access.
So where is the problem? I have installed the latest version.
Recreating podman machine doesn't help.
Creating additional bridge network also couldn't help.
Windows 10
WSL2
Steps to reproduce the issue
Steps to reproduce the issue
podman machine init --rootful
podman start
podman run -it
ping 8.8.8.8 or other ip or domain
Describe the results you received
Cannot connect to any external address if container is created on bridge network in rootful podman.
Describe the results you expected
Internet connectivity should work normally on bridge network in rootful podman.
podman info output
Client: Podman EngineVersion: 5.3.0API Version: 5.3.0Go Version: go1.23.3Git Commit: 874bf2c301ecf0ba645f1bb45f81966cc755b7daBuilt: Wed Nov 13 14:19:59 2024OS/Arch: windows/amd64Server: Podman EngineVersion: 5.3.1API Version: 5.3.1Go Version: go1.22.7Built: Thu Nov 21 01:00:00 2024OS/Arch: linux/amd64PS C:\Users\kasprowk> podman infohost:
arch: amd64buildahVersion: 1.38.0cgroupControllers:
- cpuset
- cpu
- cpuacct
- blkio
- memory
- devices
- freezer
- net_cls
- perf_event
- net_prio
- hugetlb
- pids
- rdma
- misccgroupManager: cgroupfscgroupVersion: v1conmon:
package: conmon-2.1.12-2.fc40.x86_64path: /usr/bin/conmonversion: 'conmon version 2.1.12, commit: 'cpuUtilization:
idlePercent: 99.33systemPercent: 0.39userPercent: 0.29cpus: 16databaseBackend: sqlitedistribution:
distribution: fedoravariant: containerversion: "40"eventLogger: journaldfreeLocks: 2048hostname: WRO-xxxxx-L1idMappings:
gidmap: nulluidmap: nullkernel: 5.15.153.1-microsoft-standard-WSL2linkmode: dynamiclogDriver: journaldmemFree: 9704824832memTotal: 10431590400networkBackend: netavarknetworkBackendInfo:
backend: netavarkdns:
package: aardvark-dns-1.13.1-1.fc40.x86_64path: /usr/libexec/podman/aardvark-dnsversion: aardvark-dns 1.13.1package: netavark-1.13.1-1.fc40.x86_64path: /usr/libexec/podman/netavarkversion: netavark 1.13.1ociRuntime:
name: crunpackage: crun-1.19.1-1.fc40.x86_64path: /usr/bin/crunversion: |- crun version 1.19.1 commit: 3e32a70c93f5aa5fea69b50256cca7fd4aa23c80 rundir: /run/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt-0^20241211.g09478d5-1.fc40.x86_64version: | pasta 0^20241211.g09478d5-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/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: falseseccompEnabled: trueseccompProfilePath: /usr/share/containers/seccomp.jsonselinuxEnabled: falseserviceIsRemote: trueslirp4netns:
executable: ""package: ""version: ""swapFree: 3221225472swapTotal: 3221225472uptime: 0h 1m 51.00svariant: ""plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries:
search:
- docker.iostore:
configFile: /usr/share/containers/storage.confcontainerStore:
number: 0paused: 0running: 0stopped: 0graphDriverName: overlaygraphOptions:
overlay.imagestore: /usr/lib/containers/storageoverlay.mountopt: nodev,metacopy=ongraphRoot: /var/lib/containers/storagegraphRootAllocated: 1081101176832graphRootUsed: 877125632graphStatus:
Backing Filesystem: extfsNative Overlay Diff: "false"Supports d_type: "true"Supports shifting: "false"Supports volatile: "true"Using metacopy: "true"imageCopyTmpDir: /var/tmpimageStore:
number: 0runRoot: /run/containers/storagetransientStore: falsevolumePath: /var/lib/containers/storage/volumesversion:
APIVersion: 5.3.1Built: 1732147200BuiltTime: Thu Nov 21 01:00:00 2024GitCommit: ""GoVersion: go1.22.7Os: linuxOsArch: linux/amd64Version: 5.3.1
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
WSL2 on windows 10
Additional information
No response
The text was updated successfully, but these errors were encountered:
kind/bugCategorizes issue or PR as related to a bug.networkNetworking related issue or featureremoteProblem is in podman-remotewindowsissue/bug on Windows
Issue Description
Hi,
I have a problem with rootful podman, when I create container on default bridge network I can't access the internet, it is not a dns issue, because I can't even ping ip addresses like 8.8.8.8. Only solution is creating container with --network host then internet access works.
When I login manually to machine wsl -d podman-machine-default everything work correctly.
This problem doesn't occur on rootless podman, then containers on bridge network have internet access.
So where is the problem? I have installed the latest version.
Recreating podman machine doesn't help.
Creating additional bridge network also couldn't help.
Windows 10
WSL2
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Cannot connect to any external address if container is created on bridge network in rootful podman.
Describe the results you expected
Internet connectivity should work normally on bridge network in rootful podman.
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
WSL2 on windows 10
Additional information
No response
The text was updated successfully, but these errors were encountered: