You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Many thanks for maintaining those base images.
I noticed that the file /etc/machine-id was set to 2f59308c746c49e29cc2b9997ddb22da
Would it be possible to reset it to an empty file in the base image to make sure that systemd will reinitialise it?
Here is my current workaround:
marcus.vm.provision :shell, name: 'set fleet_public_ip',
inline: <<eos
# The box we are using has unfortunately a hardcoded machine-id.
# We must not have multiple machines in the cluster with the same machine-id.
if [ "2f59308c746c49e29cc2b9997ddb22da" = "$(cat /etc/machine-id)" ]; then
echo "Must reset the /etc/machine-id and reboot. Please run 'vagrant up marcus1 --provision' again"
echo "" > /etc/machine-id
sudo poweroff
fi
eos
Thanks!
The text was updated successfully, but these errors were encountered:
The machine-id file is now removed in the cleanup script. This will prevent it from being generated by systemd at boot time, causing systemd-journald and systemd-tmpfiles-setup* services to fail.
When /etc/machine-id is an empty file, systemd will generate the machine-id automatically. So, it's better to use the code suggested by @hmalphettes.
Hi! Many thanks for maintaining those base images.
I noticed that the file
/etc/machine-id
was set to2f59308c746c49e29cc2b9997ddb22da
Would it be possible to reset it to an empty file in the base image to make sure that systemd will reinitialise it?
Here is my current workaround:
Thanks!
The text was updated successfully, but these errors were encountered: