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.

Sign up for GitHub

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

Jump to bottom

docs: Mention logical root mount point #628

Merged
merged 1 commit into from
Jun 23, 2024
Merged

docs: Mention logical root mount point #628

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/src/filesystem-sysroot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,10 @@ In the future, this functionality will be exposed and used by `bootc`.
## /sysroot mount

When booted, the physical root will be available at `/sysroot` as a
read-only mount point. This is a key aspect of how `bootc upgrade` operates:
it fetches the updated container image and writes new files to `/sysroot/ostree`.
read-only mount point and the logical root `/` will be a bind mount
pointing to a deployment directory under `/sysroot/ostree`. This is a
key aspect of how `bootc upgrade` operates: it fetches the updated
container image and writes new files to `/sysroot/ostree`.

Beyond that and debugging/introspection, there are few use cases for tooling to
operate on the physical root.
Expand Down