3 ms·
I concur as a user of Docker. Trying to get a legacy application running on Docker went smoothly. That is until I tried to start a simple rpcbind service and di
by elcritch 10y ago
I concur as a user of Docker. Trying to get a legacy application running on Docker went smoothly. That is until I tried to start a simple rpcbind service and discovered that during my time away from software development and linux that systemd had taken over plain old kludgy (but hackable!) sysV init scripts. Trying to get a dead simple service running took hours because systemd segfaults instead of gracefully handling and reporting errors. In this case, cgroups wasn't mounted, though why a system init system has a hard requirement on a relatively new kernel feature set not needed in this situation, I can't fathom. Eventually I found a shim for cgroups, but seriously it was a pain. I lost half a night's sleep due to shoddy system level programming you mention from systemd. I'm currently highly eager for FreeBSD 11.0 to reach code freeze. It has a new Docker / linux64 layer and _no_ systemd.
- cyphar 10y ago> I'm currently highly eager for FreeBSD 11.0 to reach code freeze. It has a new Docker / linux64 layer and _no_ systemd. For what it's worth, if you find a distro that doesn't have systemd you can run Docker and runC on it -- both use the underlying kernel primitives themselves and aren't wrappers for systemd scripts.
- elcritch 10y agoTrue, that's also a good point. Alas, many of the non-systemd Linux distros have pretty small communities. Do you have any preferred distro's for this?