-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mkosi: machine ID in initrd and host are different?? #32908
Comments
We always remove the machine ID from the image, so this seems like it would be a problem in systemd. |
If machine ID is previously stored at /run/machine-id, then let's reuse it. This is important on switching root and /etc/machine-id was previously a mount point. Fixes systemd#32908.
If machine ID is previously stored at /run/machine-id, then let's reuse it. This is important on switching root and /etc/machine-id was previously a mount point. Fixes systemd#32908.
If machine ID is previously stored at /run/machine-id, then let's reuse it. This is important on switching root and /etc/machine-id was previously a mount point. Fixes systemd#32908.
If machine ID is previously stored at /run/machine-id, then let's reuse it. This is important on switching root and /etc/machine-id was previously a mount point. Fixes systemd#32908.
This is actually the common case in environments where the initrd is generically built: it's not parameterized and hence comes up with a different machine ID each time. This is a fundamental different I see between switch-root and soft-reboot btw: i think switch-root should expect the machine ID to change, and soft-reboot should expect the machine ID to not change. i.e. the former is about changing from one OS to another. While the latter is about cycling the same OS. that is a relatively weak rule i believe however, i.e. it should be OK (and maybe even good) to propagate the machine ID from initrd to host (and vice versa) if we can. And for transient systems it should probably even be ok to change the machine ID on soft reboots i guess. If we wanted to make sure that initrd and host carry the same initrds i think we need to do two things:
If we have both in place, then this would mean we'd be able to have the same machine IDs persistently in both worlds. |
There are two journal directories.
If that's intentional, feel free to close. cc @DaanDeMeyer
The text was updated successfully, but these errors were encountered: