this post was submitted on 23 Jun 2026
13 points (93.3% liked)

Selfhosted

60074 readers
729 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
13
Which caddy docker builds to use? (piefed.social)
submitted 11 hours ago by anytimesoon@piefed.social to c/selfhosted@lemmy.world
12 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] ryper@lemmy.ca 5 points 10 hours ago (3 children)

You could just build it yourself, there's not much to it.

Dockerfile:

ARG VERSION=2

FROM caddy:${VERSION}-builder AS builder

RUN xcaddy build \
    --with github.com/caddy-dns/cloudflare

FROM caddy:${VERSION}

COPY --from=builder /usr/bin/caddy /usr/bin/caddy

My Dockerfile is under dockerfile-dns and then in docker-compose.yaml instead of pointing to an image I have:

services:
  caddy:
    build: ./dockerfile-dns

I'm not 100% sure of the right way to update it, but I think I usually use something like docker compose build --pull --no-cache.

[–] AzuraTheSpellkissed@lemmy.blahaj.zone 2 points 5 hours ago

I'm not entirely sure, but I think you can skip the "--no-cache" as it seems to still check for image updates. It helps to speed things up, especially if you check for updates more frequently.

[–] anytimesoon@piefed.social 2 points 9 hours ago (2 children)

This is basically the dockerfile these projects provide, so I guess I could do this myself. How do you keep the caddy container up to date? I have tugtainer (something like watchtower) update caddy automatically, but I guess this set up would break that

[–] irmadlad@lemmy.world 1 points 4 hours ago

I have tugtainer (something like watchtower) update caddy automatically, but I guess this set up would break that

Does tugtainer (always makes me giggle) have to ability to label containers for exclusion like watchtower does?

[–] ryper@lemmy.ca 3 points 9 hours ago

I can't help you with automation. I update my containers manually, whenever I think to do it. Nothing is accessible outside my network so I'm not worried about staying on top of security updates.

[–] hellmo_luciferrari@lemmy.zip 1 points 10 hours ago* (last edited 10 hours ago)

I have a Dockerifle like that:

ARG CADDY_VERSION=2.11.3
FROM caddy:${CADDY_VERSION}-builder-alpine AS builder

RUN xcaddy build \
    --with github.com/caddy-dns/cloudflare

FROM caddy:${CADDY_VERSION}-alpine

COPY --from=builder /usr/bin/caddy /usr/bin/caddy

and the docker-compose.yml file I use:

services:
  caddy:
    pull_policy: build
    build:
      context: .

And to build new versions I modify the Dockerfile after doing a docker compose down, and then to build the new version I use docker compose up.