1. Caddy version: v2.6.2 compose: name: caddy services: caddy: container_name: caddy environment: DOMAIN: domain.duckdns.org DUCKDNS_TOKEN: token EMAIL: mymail@mail.com LOG_FILE: /data/access.log image: caddy networks: default: null ports: - …

See this article: [image] How to use DNS provider modules in Caddy 2 Wiki Caddy 2 uses a new and improved DNS provider interface for solving the ACME DNS challenge. All you have to do is plug the service provider(s) you need into your build, then add the DN…

thanks for the reply, but both links refer to xcaddy, do I need to install that on the host machine?

No, xcaddy is run within the container when it’s built from the Dockerfile.

OK, seeing as I never built a docker from a repo before only from my images or just downloaded ones from the hub, I have one question: FROM caddy:<version>-builder AS builder RUN xcaddy build \ --with github.com/caddyserver/nginx-adapter \ --with github.com/hairyhenderson/caddy-teapot-modu…

You add that to a file called Dockerfile. Then you build a docker image using that Dockerfile as the instructions. I suggest you read some guides to learn about Docker. I can’t reasonably spend time here to teach the basics of Docker. The information is out there on the internet.

OK, I did not expect you to, but I did want to point out the assumptions in that guide you sent me. It assumes you know 90% of the process, and skips information like this.

Using Caddy with plugins is inherently a more advanced thing to do. Documentation can’t always assume you know nothing, because then every piece of documentation would need to be very long and repetitive, and a waste of time for the doc writers and readers who already understand. It’s best to only …

Caddy Docker with DuckDNS

Help

francislavoie (Francis Lavoie) January 27, 2023, 9:11am 2

See this article:

You need to build Caddy with the DNS plugin added. See the docs on caddy - Official Image | Docker Hub, the “Adding custom Caddy modules” section in particular.