I reinstalled Docker and finally got rootless mode working. My goal is to run a playit tunnel in one container and a Minecraft server in another, using rootless Docker. This setup works normally when Docker runs in rootful mode, but repeating the same configuration under rootless mode fails when starting the container with: "failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF". I've been troubleshooting this for several days and would appreciate ideas on what rootless-specific setting, permission, or container requirement might be causing the failure.
1 Answer
Rootless Docker reduces the risk from the Docker daemon and from a process escaping a container with root privileges. It can also expose compatibility issues with containers that expect root-level capabilities, privileged networking, device access, or unrestricted bind mounts. Since this works in rootful mode, compare the container’s required capabilities, mounted paths, and networking options first; one of those may not be available to an unprivileged user.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures