Repository navigation
Docs growfs - #2610
Open
jmarrero wants to merge 2 commits into
Open
Docs growfs#2610jmarrero wants to merge 2 commits into
jmarrero wants to merge 2 commits into
Conversation
The text predates composefs and still says / is a bind mount of the deployment directory. With composefs enabled, which the docs recommend and the composefs backend always uses, / is a composefs mount instead, and its mount source is no longer the root block device. That matters for tools that look at / to find the disk. Assisted-by: AI Signed-off-by: Joseph Marrero Corchado <jmarrero@redhat.com>
There was a problem hiding this comment.
🟡 Changes recommended
The upgrade description incorrectly states that composefs image files are stored in an OSTree repository rather than /sysroot/composefs, so the storage location needs to be qualified by backend.
1 open issue
What changed in this PR
Clarifies that growing a root filesystem on a larger disk is the image’s responsibility, not bootc’s, helping custom and minimal image authors choose suitable tooling.
Changes:
- Documents existing growth services and cloud-init limitations with composefs.
- Clarifies logical-root mounts and corrects the
systemd-growfscommand name. - Links installation and image-authoring guidance to the expansion documentation.
| File | Description |
|---|---|
docs/src/bootc-sysroot.7.md |
Expands filesystem-growth guidance and clarifies composefs mounts. |
docs/src/bootc-installation.7.md |
Links provisioning guidance to filesystem expansion. |
docs/src/bootc-compatible-images.7.md |
Explains image authors’ responsibility for filesystem growth. |
Review effort: Balanced
Base image authors need to know that disk images booted on larger disks, as in the cloud, need their root grown, and that bootc leaves this to the image. Provisioning tools are often assumed to take care of it, but the image based systems that do it (the Fedora and CentOS Stream bootc base images, Fedora CoreOS, Flatcar) each use a separate service, and cloud-init's growpart and resizefs can't find the device when / is a composefs mount. Point to those services and their docs from bootc-sysroot(7), note that minimal image variants may need one layered in, and link there from the image requirements and provisioning sections. Also fix the systemd-growfs typo. Assisted-by: AI Signed-off-by: Joseph Marrero Corchado <jmarrero@redhat.com>
This was referenced Nov 1, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#2465 showed it isn't obvious who grows the root filesystem when a bootc disk image boots on a bigger disk: bootc doesn't, and whether it happens depends on what the base image ships. I'd like the docs to say that plainly for base image authors and point at what exists today, so anyone building a custom or minimal image knows they need to bring their own.