flatcar: document sysext usage#1077
Open
kartikjoshi21 wants to merge 2 commits into
Open
Conversation
Add a Flatcar sysext example and document the build, install, and version-pinning workflow for flatcar/testing/sysext. Add coverage that the default Flatcar target continues to use the Noble-backed worker path. Signed-off-by: Kartik Joshi <karikjoshi21@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds Flatcar support to DALec’s system extension docs and examples, and validates the Flatcar default configuration via tests.
Changes:
- Document Flatcar as a supported target and add a Flatcar system extensions guide section.
- Add a Flatcar sysext example spec (
flatcar-sysext.yml) demonstrating build + install workflow. - Add tests asserting Flatcar’s default base config and worker-target behavior.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| website/docs/targets.md | Lists the new flatcar target in the documentation. |
| website/docs/system-extensions.md | Adds Flatcar-specific system extension instructions and build args. |
| targets/linux/flatcar/flatcar_test.go | Adds unit tests to verify Flatcar default base/worker behavior. |
| docs/examples/flatcar-sysext.yml | Provides an example Flatcar sysext spec used in docs. |
Comment on lines
+25
to
+27
| if DefaultConfig.Base != ubuntu.NobleConfig { | ||
| t.Fatalf("expected default Flatcar base to be Noble") | ||
| } |
Comment on lines
+64
to
+68
| sudo mkdir -p /etc/extensions | ||
| sudo cp _out/flatcar-hello.raw /etc/extensions/flatcar-hello.raw | ||
| sudo systemd-sysext status | ||
| sudo systemd-sysext merge | ||
| flatcar-hello |
Signed-off-by: Kartik Joshi <karikjoshi21@gmail.com>
kartikjoshi21
force-pushed
the
kartikjoshi21/flatcar-docs-validation
branch
from
4ccf79f to
b757279
Compare
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.
Summary
Validation
The integration test builds
flatcar/testing/sysext, verifies the generated.rawimage, extracts it withfsck.erofs, and validates its binary contents and Flatcarextension-releasemetadata.It covers both default
SYSEXT_LEVELmatching andVERSION_ID-pinned matching.Note
This validates the artifact Flatcar consumes, but does not boot a Flatcar VM or run
systemd-sysext mergeon a live Flatcar host.