Repository navigation
apko: publish -dev image variant, keep default tags minimal - #22440
Closed
falcorocks wants to merge 1 commit into
Closed
falcorocks wants to merge 1 commit into
falcorocks wants to merge 1 commit into
Conversation
Move apk-tools out of the default apko configs into per-image -dev overlays that include the base config and add apk-tools. Default tags now publish minimal images; a -dev tag carrying apk-tools is published alongside, driven by an apko_configs list per image in the catalog. Bump the factory pin to the revision that supports apko_configs fan-out and the tag-suffix input. No extra melange build legs: -dev variants reuse the same prebuilt APKs.
falcorocks
force-pushed
the
falcorocks/apko-minimal-default-dev-variant
branch
from
August 17, 2026 12:09
40d503c to
ea4b5f0
Compare
raffaele-oplabs
approved these changes
Aug 17, 2026
Contributor
Author
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
2 participants
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.
What
apk-toolsout of the defaultapko/*.yamlconfigs into per-imageapko/<svc>-dev.yamloverlays — each is a pure-YAML apkoinclude:of the base plusapk-tools, so the base stays the single source of truth.apko_configs: [base, -dev]per image in.github/images.apko.json, publishing both the default tag (minimal) and a-devtag (withapk-tools) to the same repo.apko-config+tag-suffixthroughbuild-images.apko.yamland pin the factory reusable workflows to the release that supportsapko_configs.busyboxstays in the default images.Result
<image>:<tag>— minimal (noapk-tools, no apk DB)<image>:<tag>-dev— includesapk-toolsNo extra melange build legs:
-devvariants reuse the same prebuilt APKs.