Which caddy docker builds to use?

2026-06-23 14:30 UTC

I’m looking into setting up https for my local services. Everything is currently set up using the official caddy docker image. I want to use now connect caddy to cloudflare to resolve the DNS 01. It looks like this is possible with a drop in replacement for caddy from either https://github.com/CaddyBuilds/caddy-cloudflare or https://github.com/serfriz/caddy-custom-builds Is anyone here using these builds? Are they reliable? Is there an alternative I havent considered?

Replies (2)

@sandwichsaregood@lemmy.world 2026-06-24 04:20

I ended up building it myself, which may be the best option if you want to use other plugins. I have it set up in my own Forgejo with a CI configuration to auto build the binary and docker image. Forgejo let’s you also host container images, so I can just pull from the latest build wherever I need it.

Open ##3507838
@stratself@lemdro.id 2026-06-24 05:24

I custom-build the Caddy container since it is easy to do with xcaddy. It is automated to run every week via Forgejo Actions on a Forgejo repo, and one can pull the latest images from there using Portainer or whatever docker updater software there is. You can also use any other CI/CD solutions you like as long as it churn out a regularly updated image. Github Actions is another good one if you don’t wanna set up Forgejo. The caddy-cloudflare image is probably also enough for your use case, assuming they’re regularly updated and has no vulnerabilities. But if you like control, CI is one way to go.

Open ##3513834