-
Notifications
You must be signed in to change notification settings - Fork 296
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
Seed /var behaviour and separate /var filesystems #3222
Comments
For things doing an install, they can ensure that
Which gets to the point of how they're doing that separate I'm OK doing this on firstboot, though I am a bit wary of latency (especially on systems without reflinks). From an implementation perspective...I think we'd need to run very early, |
In #3166, we changed semantics to have
/var
be valid in an OSTree commit, which is then copied into the stateroot/var
at deployment time.However, if anyone is doing separate
/var
filesystems (or really, any subpath of/var
which has seed content in the OSTree), the new/var
will not hold that seed content.It sounds like it would be more correct to make the
/var
seeding happen on first boot instead of at deployment time.The text was updated successfully, but these errors were encountered: