systemd-nspawn tries to mount /dev/pts inside a container with options "newinstance,ptmxmode=0666", which are valid only if kernel is compiled with CONFIG_DEVPTS_MULTIPLE_INSTANCES. From the journal: systemd-machined[25079]: New machine build. systemd[1]: Starting Container build. systemd[1]: Started Container build. kernel: devpts: called with bogus options
Yeah, I ran into that myself. Given that systemd-nspawn is a developer-oriented tool, I am not sure that a kernel check in the ebuild is appropriate. systemd-nspawn also uses several namespace features: CONFIG_UTS_NS CONFIG_IPC_NS CONFIG_PID_NS CONFIG_NET_NS
Can't systemd units have the same issues, assuming they use some of the more advanced options systemd gives them?
I don't think there are any unit options requiring CONFIG_DEVPTS_MULTIPLE_INSTANCES. A unit with PrivateNetwork=true would require CONFIG_NET_NS. Not sure on the others.
(In reply to Mike Gilbert from comment #3) > I don't think there are any unit options requiring > CONFIG_DEVPTS_MULTIPLE_INSTANCES. Yes. Seems it is only needed for systemd-nspawn
(In reply to Mike Gilbert from comment #1) > Yeah, I ran into that myself. Given that systemd-nspawn is a > developer-oriented tool, I am not sure that a kernel check in the ebuild is > appropriate. OK, agreed. Too many checks for a small tool used by a few people. > > systemd-nspawn also uses several namespace features: > > CONFIG_UTS_NS > CONFIG_IPC_NS > CONFIG_PID_NS > CONFIG_NET_NS And it's probably incompatible with several GRKERNSEC_CHROOT_* options (taken fom lxc ebuild): ~!GRKERNSEC_CHROOT_MOUNT ~!GRKERNSEC_CHROOT_DOUBLE ~!GRKERNSEC_CHROOT_PIVOT ~!GRKERNSEC_CHROOT_CHMOD ~!GRKERNSEC_CHROOT_CAPS
This would've saved me loads of time :/
Something like einfo at least would be nice.
Sorry, but I just don't think it makes sense to warn everybody about something that only developers would care about.