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
The current spec mandates that var-partitions are only mounted "under the condition that its partition UUID matches the first 128 bits of HMAC-SHA256(machine-id, 0x4d21b016b53445c2a9fb5c16e091fd2d)".
This is problematic for image-based appliances with a hermetic usr-partition and a tmpfs for root. In that scenario there is no sensible way to persist the machine-id. Especially for single-OS installations the requirement that the machine-id and partition UUID must match is useless and one should be able to ignore that. This could be for example a new partition type or a GPT flag.
Somewhat related is where I already explained a possible solution using a GPT flag: #117 (comment).
The text was updated successfully, but these errors were encountered:
The current spec mandates that var-partitions are only mounted "under the condition that its partition UUID matches the first 128 bits of HMAC-SHA256(machine-id, 0x4d21b016b53445c2a9fb5c16e091fd2d)".
This is problematic for image-based appliances with a hermetic usr-partition and a tmpfs for root. In that scenario there is no sensible way to persist the machine-id. Especially for single-OS installations the requirement that the machine-id and partition UUID must match is useless and one should be able to ignore that. This could be for example a new partition type or a GPT flag.
Somewhat related is where I already explained a possible solution using a GPT flag: #117 (comment).
The text was updated successfully, but these errors were encountered: