You didn't provide the command line or environment in which you run systemd-nspawn, so just dropping in to say that I've run it a bazillion times in sdm and have never seen this particular message.
systemd-nspawn is quite feature-rich, so not surprised that some variations could be problematic, based on the environment and switch combo.
systemd-nspawn is quite feature-rich, so not surprised that some variations could be problematic, based on the environment and switch combo.
Statistics: Posted by bls — Mon Dec 23, 2024 6:33 pm