Skip to content

feat: track the slim variant in the daily check - #3

Merged
vkartk merged 4 commits into
mainfrom
feat/slim-check
Oct 26, 2026
Merged

vkartk merged 4 commits into
mainfrom
feat/slim-check

Conversation

@vkartk

@vkartk vkartk commented Oct 26, 2026 •

Copy link
Copy Markdown
Member

The daily check now handles slim: it builds when the -slim tag is missing, and rebuilds slim when caddy-base is updated.

Based on #2. Tag v1.2.0 after this merges.

With `slim` enabled the check now requires the `X.Y.Z-slim` tag to exist with
every shipped platform (new reason `missing_variant`, so enabling slim on an
already-built version triggers the build), and the base-image comparison works
per variant: the default image against library/caddy:X.Y.Z as before, the slim
image against the base named in its Dockerfile stage, i.e. the caddy-base image
on GHCR, whose build time stands in for its push time. Enabling slim without an
`AS slim` stage is a configuration error.

The example Dockerfile gains the slim stage and the example config enables it.
The FROM-stage and image-reference parsers were removed from the caddy-base
image change. The check now only needs the slim stage's base, which must be
FROM ghcr.io/<owner>/<name>:<tag> AS slim; parse_slim_base reads it.
Base automatically changed from feat/caddy-base-image to main October 26, 2026 06:27
The builder sets XCADDY_SETCAP=1, so the copied binary already has
cap_net_bind_service. The default stage stays last so a plain
`docker build .` produces it.
@vkartk
vkartk merged commit d0ca5a3 into main Oct 26, 2026
1 check passed
@vkartk
vkartk deleted the feat/slim-check branch October 26, 2026 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant