Code:
Failed to register machine: Unit machine-Chroot.scope already exists.
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