FS#61862 - [systemd] generates machine-id which is not unique for containers
Attached to Project:
Arch Linux
Opened by Justin Capella (justincapella) - Monday, 25 February 2019, 21:01 GMT
Last edited by Toolybird (Toolybird) - Monday, 25 September 2023, 08:17 GMT
Opened by Justin Capella (justincapella) - Monday, 25 February 2019, 21:01 GMT
Last edited by Toolybird (Toolybird) - Monday, 25 September 2023, 08:17 GMT
|
Details
Description:
systemd-machine-id-setup does not generate unique id, causes problems with dhcp clients that use this as a client-identifier when dhcp server uses for addressing, causing vms/containers and the like to often be issued the same address causing connectivity / ARP problems. Additional info: systemd-firstboot --setup-machine-id; works to create a unique / varying id (assuming no /etc/machine-id exists), no idea why two binaries exist for the seemingly the same purpose... but the currently used one causes me grief. Steps to reproduce: Install a couple vms or archlinux containers etc, see that /etc/machine-id is not unique |
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 25 September 2023, 08:17 GMT
Reason for closing: Fixed
Additional comments about closing: Cannot repro these days.
Monday, 25 September 2023, 08:17 GMT
Reason for closing: Fixed
Additional comments about closing: Cannot repro these days.
FS#40131to use systemd-firstboot, reverted entirely inFS#41711which used uuidgen due to the bug that was eventually fixed in https://github.com/systemd/systemd/commit/07a60cc13c48c5f79616b07aad2808bfe809de22, and restored... to systemd-machine-id-setup... in systemd 218-2.In the spirit of
FS#40131I guess it makes sense to use systemd-firstboot.