The official Caddy Docker image with the added caddy-dns/cloudflare module for DNS-01 ACME validation support. This image does not change anything with Caddy except replacing the caddy
binary. Built for all supported platforms!
# Docker Hub
docker pull life8688/docker-caddy-4dns:v2.6.4
The following tags are available for the life8688/docker-caddy-4dns
image.
latest
<version>
(eg:2.6.4
, including:2.6
,2
, etc.)
Since this is built off the official Docker image all of the same Volumes, Environment variables, etc. can be used with this container. Please refer to the official Caddy Docker image and docs for more information on using Caddy.
Simply create the container as usual and include your CF_API_TOKEN
(email no longer required for API Tokens). We can utilizing Caddy's support for Environment varaiables to pass these values into our Caddyfile
.
docker run --rm -it \
--name caddy \
-p 80:80 \
-p 443:443 \
-v caddy_data:/data \
-v caddy_config:/config \
-v $PWD/Caddyfile:/etc/caddy/Caddyfile \
-e CF_API_TOKEN=UhKLc...JD9jk \
life8688/docker-caddy-4dns:v2.6.4
Then for each site you will need to add the following to your tls
directive in your Caddyfile
tls {
dns cloudflare {env.CF_API_TOKEN}
}
or via JSON
{
"module": "acme",
"challenges": {
"dns": {
"provider": {
"name": "cloudflare",
"api_token": "{env.CF_API_TOKEN}"
}
}
}
}
See the caddy-dns/cloudflare module and tls
directive for advanced usage.
You can generate a Cloudflare API token via the Cloudflare web console using the following steps:
- Login to your Dashboard
- Go to Account Profile > API Tokens
- Click "Create token" (Use the "Create Custom Token" option)
- Grant the following permissions:
Zone > Zone > Read
Zone > DNS > Edit
You can easily build the Docker image locally by doing
docker build -t docker-caddy-4dns .
See LICENSE.