On Mon, 28.04.14 17:45, Ruben Kerkhof (ru...@rubenkerkhof.com) wrote: > > Alternatively, remove the file in the container, as it will then create > > a new machine id on boot automatically, and store in the file. > > Tried that, it does generate a machine-id, but the same one as on the host. > > [ruben@vm ~]$ sudo rm testcontainer/etc/machine-id > [ruben@vm ~]$ sudo systemd-nspawn -bD ~/testcontainer > > And on the third line, the boot output shows: > Initializing machine ID from KVM UUID.
Oh yuck, this looks like a bug in systemd. Currently if /etc/machine-id is missing we will try to initialize it from the UUID that KVM maintaines for each machine. However, this is a bad idea if we are actually running inside a container already... I fixed this now in 984233ceb6dfeecd8b43864795a660a200e4ac78 (I hope). Please verify. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
