Package: podman Version: 5.2.1+ds1-2 Severity: normal X-Debbugs-Cc: u...@knuples.net
Hi, Using podman in a rootless environment (such as non-root user) on i686 causes containers to have no networking access when using pasta. Containers are brought up, but they have no networking. Switching networking to slirp4netns seems to alleviate the issue, so that's a workaround I'm using for now. Interestingly, this kernel message pops up every time an container is brought up as an non-root user: [ 361.611472] audit: type=1326 audit(1723988353.266:23): auid=1000 uid=1000 gid=1000 ses=1 subj=pasta pid=1394 comm="pasta" exe="/usr/bin/pasta" sig=31 arch=40000003 syscall=403 compat=0 ip=0xb7fb0579 code=0x80000000 For easier reproducability, this issue seems to show up in completely fresh debian sid i686 install too (tried inside VM). Not exactly sure which package is responsbile for this, so I've filed here. If problem lies somewhere else, please reassign. Best regards, Uroš -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 6.10.4-686-pae (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages podman depends on: ii conmon 2.1.10+ds1-1+b1 ii crun 1.16.1-1 ii golang-github-containers-common 0.60.1+ds1-3 ii init-system-helpers 1.66 ii libc6 2.39-7 ii libgpgme11t64 1.18.0-5 ii libseccomp2 2.5.5-1+b1 ii libsqlite3-0 3.46.1-1 ii libsubid5 1:4.16.0-4 ii netavark 1.9.0-4 Versions of packages podman recommends: ii buildah 1.37.1+ds1-2 ii ca-certificates 20240203 ii catatonit 0.1.7-1+b1 ii containers-storage 1.55.0+ds1-3 ii dbus-user-session 1.14.10-4+b1 ii passt 0.0~git20240814.61c0b0d-1 ii slirp4netns 1.2.1-1+b1 ii uidmap 1:4.16.0-4 Versions of packages podman suggests: ii docker-compose 1.29.2-6.3 ii iptables 1.8.10-4 -- no debconf information
