Rootless Podman IP address space overlap with host #18081
-
Hi, I have a project using Podman which is working on Arch Linux (my computer) and Ubuntu (in Github Actions). To further test its portability. I am trying to run Podman in a Fedora Silverblue 37 VM. After a fresh install of Fedora Silverblue 37 I upgraded Podman to version 4.4.4 by running
It does work with rootful Podman:
I noticed that the IP address for
I've tried some various things, none of which worked:
Comparing host:
arch: amd64
buildahVersion: 1.29.0
cgroupControllers:
- cpu
- io
- memory
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.1.7-2.fc37.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.1.7, commit: '
cpuUtilization:
idlePercent: 94.62
systemPercent: 1.53
userPercent: 3.85
cpus: 20
distribution:
distribution: fedora
variant: silverblue
version: "37"
eventLogger: journald
hostname: fedora
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 6.2.9-200.fc37.x86_64
linkmode: dynamic
logDriver: journald
memFree: 2105700352
memTotal: 8308289536
networkBackend: netavark
ociRuntime:
name: crun
package: crun-1.8.3-2.fc37.x86_64
path: /usr/bin/crun
version: |-
crun version 1.8.3
commit: 59f2beb7efb0d35611d5818fd0311883676f6f7e
rundir: /run/user/1000/crun
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
os: linux
remoteSocket:
exists: true
path: /run/user/1000/podman/podman.sock
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: true
serviceIsRemote: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.2.0-8.fc37.x86_64
version: |-
slirp4netns version 1.2.0
commit: 656041d45cfca7a4176f6b7eed9e4fe6c11e8383
libslirp: 4.7.0
SLIRP_CONFIG_VERSION_MAX: 4
libseccomp: 2.5.3
swapFree: 6464729088
swapTotal: 8307863552
uptime: 1h 60m 53.00s (Approximately 0.04 days)
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
volume:
- local
registries:
search:
- registry.fedoraproject.org
- registry.access.redhat.com
- docker.io
- quay.io
store:
configFile: /var/home/chris/.config/containers/storage.conf
containerStore:
number: 18
paused: 0
running: 14
stopped: 4
graphDriverName: overlay
graphOptions: {}
graphRoot: /var/home/chris/.local/share/containers/storage
graphRootAllocated: 41872785408
graphRootUsed: 17441189888
graphStatus:
Backing Filesystem: btrfs
Native Overlay Diff: "true"
Supports d_type: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 13
runRoot: /run/user/1000/containers
transientStore: false
volumePath: /var/home/chris/.local/share/containers/storage/volumes
version:
APIVersion: 4.4.4
Built: 1680521485
BuiltTime: Mon Apr 3 07:31:25 2023
GitCommit: ""
GoVersion: go1.19.7
Os: linux
OsArch: linux/amd64
Version: 4.4.4 How else can I debug? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I assume your host ip is |
Beta Was this translation helpful? Give feedback.
I assume your host ip is
10.0.2.15
.You cannot reach ips in the
10.0.2.0/24
by default because this is the default subnet which is used by slirp4netns in the container.You have to change the slirp4netns subnet to something different, see https://blog.podman.io/2023/02/default-podman-network-subnets/