Make sure /etc/machine-id is unique on cloned VMs

[Ram Janovski]

if you copy a CoreOS VM (that has already booted once), you'll get a copy with the same machine-id. BAD--Fleet will fail.

to fix the cloned VM:

sudo rm /etc/machine-id

sudo systemctl reboot

[Kelsey Hightower]

Yeah this is comment when creating VMware templates. Most people have a clean up script they run before shutting down the "base" VM before using it as a template.

[Darren Shepherd]

This is a totally not helpful comment, but in general, don't copy CoreOS VMs.  Its better to follow the OEM approach of populating /usr/share/oem or OEM partition if you want to create a "golden image" than to make templates from existing booted VMs.

But it is good for users to know that the machine-id does need to be unique.

Darren

--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.