▲ 27 ▼ Which caddy docker builds to use? (piefed.social) submitted 4 months ago by anytimesoon@piefed.social to c/selfhosted@lemmy.world 20 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?
[–] anytimesoon@piefed.social [S] 1 point 4 months ago (2 children) That seems like a good option. How do you keep it updated? permalink fedilink source parent hideshow 2 child comments replies: [–] hellmo_luciferrari@lemmy.zip 2 points 4 months ago* (1 child) I have a Dockerifle: 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 have this snippet at the top, of course this isn't the full file as there are specifics to my usecase in my full yml: 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.`` Though this is outdated for my current setup, as I also use github.com/lucaslorentz/caddy-docker-proxy by adding "--with github.com/lucaslorentz/caddy-docker-proxy/v2" below where I added the Cloudflare repo. This is so I can use Docker Labels to to automate entries. permalink fedilink source parent hideshow 1 child comment replies: [–] AzuraTheSpellkissed@lemmy.blahaj.zone 2 points 4 months ago Note that the (non-windows) caddy and caddy: builder images are all alpine based. The "-alpine" tags point to the same images (as you can tell by the hashes). But some like to be explicit about it 💜. permalink fedilink source parent
[–] hellmo_luciferrari@lemmy.zip 2 points 4 months ago* (1 child) I have a Dockerifle: 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 have this snippet at the top, of course this isn't the full file as there are specifics to my usecase in my full yml: 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.`` Though this is outdated for my current setup, as I also use github.com/lucaslorentz/caddy-docker-proxy by adding "--with github.com/lucaslorentz/caddy-docker-proxy/v2" below where I added the Cloudflare repo. This is so I can use Docker Labels to to automate entries. permalink fedilink source parent hideshow 1 child comment replies: [–] AzuraTheSpellkissed@lemmy.blahaj.zone 2 points 4 months ago Note that the (non-windows) caddy and caddy: builder images are all alpine based. The "-alpine" tags point to the same images (as you can tell by the hashes). But some like to be explicit about it 💜. permalink fedilink source parent
[–] AzuraTheSpellkissed@lemmy.blahaj.zone 2 points 4 months ago Note that the (non-windows) caddy and caddy: builder images are all alpine based. The "-alpine" tags point to the same images (as you can tell by the hashes). But some like to be explicit about it 💜. permalink fedilink source parent