Podman: rawhide: rootless: podman run broken: slirp4netns failed

Created on 12 Aug 2019  路  16Comments  路  Source: containers/podman

On latest & greatest rawhide:

$ podman run --rm  alpine date
Error: slirp4netns failed

Debug log attached, but there is no useful trace of the actual slirp4netns invocation. There are cgroup warnings at the end.

Side note: I also saw, on the very first rootless run:

WARN[0000] Error initializing configured OCI runtime crun: no valid executable found for OCI runtime crun: invalid argument

No idea if this is related.

podman-1.5.1-0.3.dev.git3bc861c.fc31
slirp4netns-0.4.0-20.1.dev.gitbbd6f25.fc31
kernel-5.3.0-0.rc3.git1.1.fc31
runc-1.0.0-98.dev.git2e94378.fc31

podman-slirp4netns-failed.log

do-not-close kinbug rootless stale-issue

All 16 comments

The warn line is fine - we're shipping a config that includes crun but it's not a hard dependency of the package, so if it's not available, we throw a warning in the logs and don't allow using it.

@giuseppe PTAL

Still failing with latest 1.5.1-0.8.dev.gitec93c9d.fc31 build (click /tmp/package-test.sh 12m11s and scroll to line 470) (yes, I know the line is green and should be red. That seems to have started happening last week. I'm hoping it'll get fixed). ec93c9d8 is from just a little while ago today.

@giuseppe PTAL

slirp4netns cannot open /dev/net/tun. The file has the wrong permissions:

$ ls -l /dev/net/tun
crw-------. 1 root root 10, 200 Aug 13 11:56 /dev/net/tun

If I change it to 666 then it works fine.

It looks like a regression in udev. Could you file a bug?

Yes this looks like a bug.

~I'm~ I was trying to narrow down the conditions causing breakage, by dnf-upgrading and identifying the components that cause it. It is not going well (partial dnf upgrades on rawhide, followed by reboot, cause reboot hangs). I'll try one last time and will update the bz with any info I can find.

I get that warn too the first time I run podman on my machine, afterwards it doesn't show up anymore, until I reboot.

A workaround for the permission issue on docker-desktop:

https://github.com/docker/for-win/issues/4627
https://github.com/docker/for-mac/issues/3838

This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days.

Cuplikan layar dari 2019-11-01 15-16-02
OS: openSUSE Leap 15.1

https://github.com/containers/libpod/pull/4350 will at least get us the output of what the error is. and this has been merged upstream. If someone could try this out and tell us why slirp4netns is failing.

1.6.3 should contain #4350, right?
Any idea when the projectatomic ppa will ship 1.6.3 for ubuntu 18.04?
I would provide the output to this bug, but I don't have the time right now to build podman myself on this machine.

@stderr-enst yes, 1.6.3 includes the changs from #4350. IDK about the shipping time to ubuntu, if anyone would it would be @lsm5

1.6.3 should contain #4350, right?
Any idea when the projectatomic ppa will ship 1.6.3 for ubuntu 18.04?
I would provide the output to this bug, but I don't have the time right now to build podman myself on this machine.

Just built the deb for 1.6.3 manually
Can confirm this issue is resolved on both Ubuntu and Debian

Was this page helpful?
0 / 5 - 0 ratings