build_library: use smaller rootfs for Akamai - #4270
Merged
Merged
Conversation
This was working fine until Linode enforced the size limit (i.e 6Gb uncompressed image). rootfs should expand to the available disk size anyway. Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
tormath1
had a problem deploying
to
development
September 10, 2026 14:14 — with 
GitHub Actions
Error
GitHub Actions
Error
tormath1
moved this to ✅ Testing / in Review
in Flatcar tactical, release planning, and roadmap
There was a problem hiding this comment.
🟢 Approval recommended
The change is minimal, consistent with existing layout fallback behavior, and directly aligns with the stated goal of reducing initial image size.
Pull request overview
Adjusts the Akamai (Linode) VM image build settings to reduce the initial root filesystem size, addressing Linode’s enforced uncompressed image size limit while still relying on runtime expansion.
Changes:
- Stop selecting the
vmdisk layout for Akamai images so the defaultbaselayout is used (smaller initial ROOT partition).
File summaries
| File | Description |
|---|---|
| build_library/vm_image_util.sh | Removes the Akamai-specific DISK_LAYOUT=vm override so Akamai images fall back to the smaller default disk layout. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
chewi
approved these changes
Sep 10, 2026
tormath1
had a problem deploying
to
development
September 11, 2026 07:57 — with
GitHub Actions
Error
GitHub Actions
Error
There was a problem hiding this comment.
🟡 Changes recommended
The Akamai image conversion has a critical layout incompatibility that must be resolved before approval.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (1)
build_library/vm_image_util.sh:233
- The PR description still leaves the changelog requirement unchecked, but this is a user-facing Linode/Akamai image-size bug fix. Please add a concise entry under
changelog/bugfixes/before merging so the fix is included in release notes.
IMG_akamai_DISK_LAYOUT=akamai
- Files reviewed: 2/2 changed files
- Comments generated: 2
- Review effort level: Lite
| "9":{ | ||
| "label":"ROOT", | ||
| "fs_label":"ROOT", | ||
| "blocks":"131072" |
|
|
||
| ## akamai (Linode) | ||
| IMG_akamai_DISK_LAYOUT=vm | ||
| IMG_akamai_DISK_LAYOUT=akamai |
tormath1
force-pushed
the
tormath1/linode
branch
from
September 11, 2026 10:22
43e715f to
59bd939
Compare
tormath1
requested a deployment
to
development
September 11, 2026 10:22 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
There was a problem hiding this comment.
🔵 Needs a closer look
Add the required changelog entry before merging.
Review details
Suppressed comments (1)
build_library/vm_image_util.sh:233
- This changes the published Akamai/Linode image layout and fixes a user-facing image-size regression, so it needs a changelog entry. The repository requires bug-fix/change entries under
changelog/for this kind of change (changelog/README.md:1-13), but the PR currently adds none; please add one before merging.
IMG_akamai_OEM_SYSEXT=akamai
- Files reviewed: 1/1 changed files
- Comments generated: 0 new
- Review effort level: Lite
tormath1
marked this pull request as ready for review
September 11, 2026 10:29
github-project-automation
Bot
moved this from ✅ Testing / in Review
to Implemented
in Flatcar tactical, release planning, and roadmap
Contributor
Author
|
Cherry-picked to:
|
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.
This was working fine until Linode enforced the size limit (i.e 6Gb uncompressed image).
rootfs should expand to the available disk size anyway.
This partially reverts: f0c94a9
This creates a raw disk of
7.88Gib:It's not ideal, but we can't lower more.
changelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.