Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 4421

Raspberry Pi OS • systemd-nspawn - weird error message

$
0
0

Code:

Failed to register machine: Unit machine-Chroot.scope already exists.
After using systemd-nspawn for a while (testing/dev, so lots of iterations - in and out, in and out, etc), eventually, this error message shows up and it no longer works. Didn't do anything that would (seem to be likely) to cause it. Possible that rebooting the host machine might fix (but probably not) and, in any case, don't want to do that (reboot the host).

Fix is: include option --register=no on the command line.

Googled the message and got lots of hits - going back as far as 2016. Nobody (to this day, AFAICT) really seems to know how/why it happens or if a real fix is possible, but the --register=no hack seems the only good workaround.

Apparently, including --register=no is OK (and, in fact, recommended) if you are not using --boot, which makes it OK for my use case(s). But it begs the question: What about Botspot and "vdesktop", where --boot is the point of the exercise? Has this issue raised its head in that situation? And, if so, how was it dealt with?

Statistics: Posted by BigRedMailbox — Mon Dec 23, 2024 12:29 pm — Replies 0 — Views 31



Viewing all articles
Browse latest Browse all 4421

Trending Articles