caddy-docker-cloudflaredns

Caddy webserver v2 in a docker with the following plugins built in:

• caddy-dns/cloudflare — Cloudflare DNS provider for ACME DNS-01 challenges.
• lucaslorentz/caddy-docker-proxy — generates the Caddyfile from labels on other Docker containers, so Caddy auto-configures itself as you start/stop services.

The docker containers are built for amd64, arm64 / aarch64, and arm/v7. Available at:

• kingpin/caddy-docker-cloudflaredns:latest (Docker Hub)
• ghcr.io/kingpin/caddy-docker-cloudflaredns:latest (GHCR)
• quay.io/kingpinx1/caddy-docker-cloudflaredns:latest (Quay)

The image ships a HEALTHCHECK that probes Caddy's admin API on 127.0.0.1:2019. If you set admin off in your Caddyfile, run with --no-healthcheck or override HEALTHCHECK in your own image.

docker run :

docker run -it --name caddy \
     -p 80:80 \
     -p 443:443 \
     -v ./caddy_data:/data \
     -v ./caddy_config:/config \
     -v ./Caddyfile:/etc/caddy/Caddyfile \
     -e CLOUDFLARE_API_TOKEN=iHFh938nf93r39jsSnS4Q5zw04q0EsRG7xmalB \
     kingpin/caddy-docker-cloudflaredns

Docker-compose.yml

services:
  caddy:
    image: ghcr.io/kingpin/caddy-docker-cloudflaredns:latest
    container_name: caddy
    environment:
      - CLOUDFLARE_API_TOKEN=iHFh938nf93r39jsSnS4Q5zw04q0EsRG7xmalB
    ports:
      - 80:80
      - 443:443
    volumes:
            - './caddy/Caddyfile:/etc/caddy/Caddyfile'
            - './caddy/caddy_data:/data'
            - './caddy/caddy_config:/config'
    restart: unless-stopped

this is a bare basic example, you may need to modify it further to suit your setup.

Get Cloudflare api token following this token : https://support.cloudflare.com/hc/en-us/articles/200167836-Managing-API-Tokens-and-Keys

edit your Caddyfile with this at the top :

{ 
    acme_dns cloudflare {env.CLOUDFLARE_API_TOKEN} 
}

Using the docker-proxy plugin

This image also bundles caddy-docker-proxy, which builds the Caddyfile from labels on your other containers — Caddy reconfigures itself automatically as you start and stop services, so you don't have to maintain a Caddyfile by hand.

To use it, run Caddy with the docker-proxy command and give it read access to the Docker socket:

services:
  caddy:
    image: ghcr.io/kingpin/caddy-docker-cloudflaredns:latest
    container_name: caddy
    command: caddy docker-proxy
    ports:
      - 80:80
      - 443:443
    environment:
      - CLOUDFLARE_API_TOKEN=iHFh938nf93r39jsSnS4Q5zw04q0EsRG7xmalB
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./caddy_data:/data
      - ./caddy_config:/config
    restart: unless-stopped

  whoami:
    image: traefik/whoami
    labels:
      caddy: whoami.example.com
      caddy.reverse_proxy: "{{upstreams 80}}"
      caddy.tls.dns: cloudflare {env.CLOUDFLARE_API_TOKEN}

With this setup, any container you label with caddy: <hostname> is published by Caddy automatically, and the caddy.tls.dns label drives DNS-01 certificates through Cloudflare. See the caddy-docker-proxy docs for the full label syntax.