Replies: 1 comment
-
Marking as a duplicate of: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am attempting to run docker rootless on compute nodes that are running RHEL 8.8 in memory. The OS is not installed to a physical disk and is running in RAM on the physical server.
Here is the system information below:
Kernel info
Linux compute_node01.example 4.18.0-477.10.1.el8_8.x86_64 #1 SMP Wed Apr 5 13:35:01 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
Docker info
Packages installed for docker:
The steps I am taking to attempt to setup dockerd-rootless
Run dockerd-rootless-setup.sh
If I change to the same user as I am already logged in as, this command executes successfully with the following output:
Then if I go to launch dockerd-rootless.sh manually, after exporting env variables, I get the following:
Which points me to a slirp4netns error, when looking at the logs, I see the following:
When investigating I notice the line:
localhost dockerd-rootless.sh[159644]: [rootlesskit:parent] error: failed to setup network &{logWriter:0xc000250ae0 binary:slirp4netns mtu:65520 ipnet:<nil> disableHostLoopback:true apiSocketPath: enableSandbox:true enableSeccomp:true enableIPv6:false ifname:tap0 infoMu:{w:{state:0 sema:0} writerSem:0 readerSem:0 readerCount:{_:{} v:0} readerWait:{_:{} v:0}} info:<nil>}: waiting for ready fd (/usr/bin/slirp4netns --mtu 65520 -r 3 --disable-host-loopback --enable-sandbox --enable-seccomp 159656 tap0): slirp4netns failed
I believe the PID (159656) that is being called is an issue? But no idea, I am stumped.
When doing these exact same steps on a normal installed VM, there are no issues at all.
Any help or troubleshooting is appreciated. I would use a different network driver, but have somewhat of a hard requirement on slirp4netns. I am also aware other softwares are more suited for rootless container execution.
Beta Was this translation helpful? Give feedback.
All reactions