To best solve this problem, remove the contents of /etc/machine-id so that it is an empty file: sudo truncate -s 0 /etc/machine-id I’ll probably study this a bit more at some point, but I wanted to get this blog entry posted quickly in case someone else is fighting this. I haven’t done a lot of reading on this yet, I did only enough research to solve the problem. I am not sure why this is the case, why someone thought this was a good idea, or the reasons why Ubuntu 18.04 is set up this way. What’s happening, is that for some reason, the machine-id is being used to request an IP address from DHCP, rather than the Mac address. It’s also common for /var/lib/dbus/machine-id to be a symbolic link to /etc/machine-id.
In addition, the machine-id may (or may not) also be stored in the following file: /var/lib/dbus/machine-id When you install a Linux distribution that utilizes machine-id (Ubuntu 18.04 is such a distribution) it will get a unique machine-id generated and stored in the following file: /etc/machine-id The root cause ended up being due to something called a “machine-id”.
My virtual machines were all running Ubuntu 18.04, though this may impact other distributions too. In my case, I am using Proxmox, though the root-cause is not specific to any virtualization package. I had a hard time finding the culprit, so I figured I would write a post about it. Each of them would be assigned the same IP address from my DHCP server, despite the fact that each VM created from my standard template had a unique Mac address. I ran into a problem recently where virtual machines I created from a template were fighting over the same IP address.
0 kommentar(er)
