Skip to content

fix(infra): build the Caddy image with pinned DNS plugins #186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
arthware-dev merged 1 commit into from
Oct 6, 2026
Merged

fix(infra): build the Caddy image with pinned DNS plugins #186

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions stacklets/infra/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,17 @@
# The hetzner module is v2, which talks to the Hetzner Cloud API. v1 used
# the DNS Console API, which Hetzner has deprecated.
#
# Pinned to the Caddy 2.10 line. Every subdomain reusing the wildcard
# certificate needs 2.10 or later.
# Pinned to the Caddy 2.11 line. Every subdomain reusing the wildcard
# certificate needs 2.10 or later, and hetzner v2 requires 2.11.2.
#
# The plugins are pinned too. Unpinned, xcaddy takes each plugin's newest
# release, and one that requires a newer Caddy breaks the build for every
# install: hetzner v2.0.0 did that to the 2.10 image.

FROM caddy:2.10-builder AS builder
FROM caddy:2.11-builder AS builder
RUN xcaddy build \
--with github.com/caddy-dns/hetzner/v2 \
--with github.com/caddy-dns/cloudflare
--with github.com/caddy-dns/hetzner/v2@v2.0.1 \
--with github.com/caddy-dns/cloudflare@v0.2.4

FROM caddy:2.10
FROM caddy:2.11
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
Loading