On 1/30/21 1:00 PM, Gena Makhomed wrote: > I can't use CentOS Stream - it is beta quality and has critical bugs. > For example: https://bugzilla.redhat.com/show_bug.cgi?id=1913806 As far as I can tell: systemd-nspawn is defaulting to a private user namespace, but no private network namespace, and that combination is not supported. If you configure a private network namespace, does that nspawn container start properly? https://www.freedesktop.org/software/systemd/man/systemd.nspawn.html#%5BNetwork%5D%20Section%20Options I'm inferring some of this, so if you've already got private network namespace configured, that's probably not the cause.