Bug#915397: systemd-container: fails to start a container going through machines.target or machinectl

[ed.gomez at free.fr]

> I assume the main difference is that you are not using a Debian
> provided
> kernel and I do?

Yes i'm running my own compiled 4.19.5 kernel, old habit of mine to use make-kpkg builds.

I'll install the standard debian kernel and give a try on next reboot (may not happen before end of the week).

In the meantime, do you have any specific kernel setting that comes to mind that can explain this odd systemd-nspawn behavior ?

-- 
Edouard Gomez