-
Notifications
You must be signed in to change notification settings - Fork 84
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
install: switch to doing dynamic mounts #826
Comments
We're looking again at the ergonomics of `bootc install to-existing-root`. This uses the "mounting into mount namespaces" from the new mount API to automatically set up `/dev` and `/var/lib/containers` if they weren't provided to `podman run`, which shrinks what's needed a bit. Closes: containers#826 Signed-off-by: Colin Walters <[email protected]>
We're looking again at the ergonomics of `bootc install to-existing-root`. This uses the "mounting into mount namespaces" from the new mount API to automatically set up `/dev` and `/var/lib/containers` if they weren't provided to `podman run`, which shrinks what's needed a bit. Closes: containers#826 Signed-off-by: Colin Walters <[email protected]>
Can we drop I tried looking into dropping Anyway without
Quite memorable With
And maybe it's a bit of a ridiculous idea but if we can selfishly convince the podman project to bundle/alias
or
|
(Sorry I'm kinda discussing BIFROST-532 instead of #826) |
Moving this to a targeted issue from #380
Basically let's switch to using dynamic mounts for e.g.
/dev
and/var/lib/containers
etc. This would help drop out a lot of the boilerplate from our install invocations.The text was updated successfully, but these errors were encountered: