At $dayjob we make a portal that starts docker jobs. For this to work we need to access the Docker API
running on the host. A typical way to make this work is to use the docker socket located in
You just mount the socket in your container and point your Docker client to it. This works on macOS and several linux distributions. It works in Production(tm).
Then my macbook pro needed servicing so I installed Fedora on my replacement and figured things would just work out.
When you want to install docker, typically you just type in the executable name of your package manager and
$ sudo dnf install docker
This command doens’t work out of the box because it asks you to install moby-engine instead. Alright you think: moby-engine is just docker right?
SELinux enters the room
Apparently moby-engine does not work with the cgroups 2 used by SELinux, or tries to do so but fails. There was no way I was able to let my docker client talk to the host through a mounted docker socket. I changed the rights, changed the groups, changed the user. So we YOLO’d the container and put it in production for testing (fortunately the application is used internally by just a couple of users a couple of days in a month). This cost me about 2 days of fiddling, reading and trying stuff. SELinux won.
Next I wanted to use testcontainers.org for testing backup/restore procedures of databases we manage through the docker application. Stepping through the code I saw that they try to start a container for reaping dangling containers that were started during testing. This requires… access to the docker socket.
I tried starting the ryuk container manually using my shell, but the only way to start it was using the privileged flag. Looking at
the code from testcontainers I noticed
they already set the container to run privileged (UPDATE Apparently my reading of the code was wrong
and I need to set a flag explicitly to let Ryuk run privileged. The documentation and the mitigation of ryuk at testcontainers is not good in this
instance IMO), so something janky was happening with SELinux.
One of the tickets mentioned reinstalling containerd, to fix the rights. Looking at some other posts they mentioned installing docker-ce.
So I followed the manual for installing docker-ce and lo and behold: everything worked immediately.
While SELinux is probably making my life as a user of Linux safer, it is frustrating that it requires you to become an expert at it before you can actually get work done. At this time I can’t say I am impressed by SELinux.