Skip to content
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

Mount BOTTLEROCKET-PRIVATE before BOTTLEROCKET-DATA #4348

Open
mikn opened this issue Dec 27, 2024 · 0 comments
Open

Mount BOTTLEROCKET-PRIVATE before BOTTLEROCKET-DATA #4348

mikn opened this issue Dec 27, 2024 · 0 comments
Labels
status/needs-triage Pending triage or re-evaluation type/enhancement New feature or request

Comments

@mikn
Copy link

mikn commented Dec 27, 2024

What I'd like:
Mount BOTTLEROCKET-PRIVATE to a path that does not require BOTTLEROCKET-DATA to first be mounted.

Currently, the BOTTLEROCKET-PRIVATE partition is inexplicably mounted after BOTTLEROCKET-DATA because of its position in the mount tree (/var/lib/bottlerocket for -PRIVATE and /local and /local/var bind mounted to /var for -DATA) - this means that the -DATA partition (which is required relatively late) must be mounted before -PRIVATE. This limits what type of data you could feed to the early boot to mount -DATA (only the kernel command line).

We would like to be able to store configuration for mounts in the private partition, specifically for cryptsetup and device mapper tables in our case.

We are currently carrying the release package in our own variant to make this possible. We do it by mounting the -PRIVATE partition under /run/bottlerocket_private (still read only) and then bind-mounting it to /var/lib/bottlerocket once the rest of the mount tree is in place.

This opens up some exciting possibilities wrt bootstrap configuration also.

Any alternatives you've considered:

  • Injecting kernel command line arguments (not feasible for device mapper tables)
  • Temporary mount of private partition in our own units (uglier and more brittle)
@mikn mikn added status/needs-triage Pending triage or re-evaluation type/enhancement New feature or request labels Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/needs-triage Pending triage or re-evaluation type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant