GitHub
ghcr.io

Upstream Project

Starting the container

cli

docker run --rm \
    --name="caddy" \
    -p 80:8080 \
    -p 443:8443 \
    -e PUID=1000 \
    -e PGID=1000 \
    -e UMASK=002 \
    -e TZ="Etc/UTC" \
    -e WEBUI_PORTS="8080/tcp,8443/tcp" \ #(3)!
    -e CUSTOM_BUILD="" \
    -v /<host_folder_config>:/config \
    ghcr.io/hotio/caddy

compose

services:
  caddy:
    container_name: caddy
    image: ghcr.io/hotio/caddy
    ports:
      - "80:8080"
      - "443:8443"
    environment:
      - PUID=1000
      - PGID=1000
      - UMASK=002
      - TZ=Etc/UTC
      - WEBUI_PORTS=8080/tcp,8443/tcp #(3)!
      - CUSTOM_BUILD
    volumes:
      - /<host_folder_config>:/config

!!! info

Included modules: [caddy-dns/cloudflare](https://github.com/caddy-dns/cloudflare), [mholt/caddy-ratelimit](https://github.com/mholt/caddy-ratelimit). The default config only allows access from private ip ranges.

Custom build

If you set the environment variable CUSTOM_BUILD to a file location like for example /config/caddy_linux_amd64_custom, an attempt is made to start Caddy with that binary. The custom build can be obtained from the Caddy download page. This is particularly useful if you need extra modules.