Caddy in Docker with Cloudflare DNS

So I’ve been using Caddy for a while as my web server/reverse proxy. Basically it sits in front of all of my services and redirects/protects my stuff.

Now I have been building a custom image off of abiosoft/caddy-docker with a custom set of plugins… manually… That changes today!

WOOT! What you are seeing here is a screenshot of docker cloud automatic image building. So basically I created a repo on GitHub that houses a Dockerfile (at the moment it’s a custom temp one cause docker cloud isn’t properly passing env variables) which when the master branch is pushed will remote trigger a build on docker hub using the Dockerfile.

alexandzors/caddy — Custom abiosoft/caddy-docker image.

So why all this you may ask. Well I really wanted to get a wildcard Let’s Encrypt SSL cert. The best way to do that is to use a supported DNS provider plugin with the following in a Caddyfile directive:

1
tls {
2
 dns cloudflare
3
}

I can then import that wildcard cert to all of my subdomain directives. Makes it easier to manage as you get one overall certificate instead of one for each subdomain + the root domain.

This custom image also has a few extra plugins besides the Cloudflare one so it’s even better!

If you want to try it out you can run sudo docker pull alexandzors/caddy. Then deploy it with the following compose file:

1
version: '3.6'
2
services:
3
  caddy:
4
    deploy:
5
      replicas: 1
6
    restart: unless-stopped
7
    healthcheck:
8
      test: ["CMD", "curl", "-I", "http://localhost"]
9
      interval: 1m30s
10
      timeout: 10s
11
      retries: 3
12
      start_period: 40s
13
    image: alexandzors/caddy
14
    ports:
15
      - "81:80"
16
      - "444:443"
17
      - "2015:2015"
18
    volumes:
19
      - /path/to/Caddyfile:/etc/Caddyfile
20
      - /path/to/caddy/dir:/root/.caddy
21
      - /path/to/sites/root:/srv
22
    environment:
23
      - ACME_AGREE=true
24
      - CLOUDFLARE_EMAIL=<CF_EMAIL>
25
      - CLOUDFLARE_API_KEY=<CF_API_KEY>