Caddy Quadlet help #28
-
I'm trying to build caddy with a dns plugin so i can use lets encrypt. My quadlet setup is nearly the same as yours except the dns plugin used. The problem seems to be that when starting caddy, it looks for a localhost registry but cannot find one/will not trigger the build. Do you know of a way around this? It appears to work if i manually run a build and then start caddy though. ## Containerfile
FROM docker.io/caddy:builder-alpine AS builder
RUN xcaddy build \
--with github.com/caddy-dns/acmedns
FROM docker.io/caddy:latest
COPY --from=builder /usr/bin/caddy /usr/bin/caddy ## caddy.build
[Build]
ImageTag=localhost/caddy-acmedns
SetWorkingDirectory=unit ## caddy.container
[Unit]
Description=Reverse proxy
[Service]
Restart=on-failure
[Install]
WantedBy=default.target
[Container]
Image=caddy.build
ContainerName=caddy
HostName=caddy
PublishPort=8080:80
PublishPort=8443:443
PublishPort=8443:443/udp
Volume=caddy-config:/config
Volume=caddy-data:/data
Volume=./Caddyfile:/etc/caddy/Caddyfile:ro
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Answering my own question after more googling. Quadlet support of .build options were merged in 5.2.0. Therefore, must wait for the release of Ubuntu 25.04 (plucky) which as of this post appears to have Podman 5.3.2. To clarify, manually running a build for the custom caddy will allow the quadlet to work. |
Beta Was this translation helpful? Give feedback.
Answering my own question after more googling. Quadlet support of .build options were merged in 5.2.0. Therefore, must wait for the release of Ubuntu 25.04 (plucky) which as of this post appears to have Podman 5.3.2. To clarify, manually running a build for the custom caddy will allow the quadlet to work.