Skip to content

Caddy Caddy

Description / nameInput element
Container Registry
Container Configuration Root Path
Timezone
Caddy Host Port
Caddy /config Path
Caddy /data Path

Build Status Last Commit

Fast, multi-platform web server and reverse proxy with automatic HTTPS, written in Go.

Port 80
Registry ghcr.io/daemonless/caddy
Daemonless daemonless/caddy
Source caddyserver/caddy
Website caddyserver.com

Version Tags

Multi-arch manifests — resolve automatically to the right image for your platform.

Tag Description Best For
latest Official upstream Caddy FreeBSD binary (auto-tracks latest release). Most users — recommended.
pkg FreeBSD Quarterly. Uses stable, tested packages. Production stability.
pkg-latest FreeBSD Latest. Rolling package updates. Staying current.
Tag Description Best For
latest-amd64 Official upstream Caddy FreeBSD binary (auto-tracks latest release). Most users — recommended.
pkg-amd64 FreeBSD Quarterly. Uses stable, tested packages. Production stability.
pkg-latest-amd64 FreeBSD Latest. Rolling package updates. Staying current.
Tag Description Best For
latest-aarch64 Official upstream Caddy FreeBSD binary (auto-tracks latest release). Most users — recommended.
pkg-aarch64 FreeBSD Quarterly. Uses stable, tested packages. Production stability.
pkg-latest-aarch64 FreeBSD Latest. Rolling package updates. Staying current.

Before deploying, ensure your host environment is ready. See the Quick Start Guide for host setup instructions, including the security model for host vs. container privileges.

Deployment

services:
  caddy:
    image: "ghcr.io/daemonless/caddy:latest"
    container_name: caddy
    environment:
      - TZ=UTC  # Timezone for the container
    volumes:
      - "/path/to/containers/caddy:/config"
      - "/path/to/containers/caddy/data:/data"
    ports:
      - "80:80"
      - "443:443"
      - "443:443"
    # always (not unless-stopped) so FreeBSD's podman rc.d auto-starts it at boot
    restart: always

Save as compose.yaml, then run podman-compose up -d.

1
2
3
4
5
6
7
8
podman run -d --name caddy \
  -p 80:80 \
  -p 443:443 \
  -p 443:443 \
  -e TZ=UTC \
  -v /path/to/containers/caddy:/config \
  -v /path/to/containers/caddy/data:/data \
  ghcr.io/daemonless/caddy:latest

Save as run.sh, then run sh run.sh.

- name: Deploy caddy
  containers.podman.podman_container:
    name: caddy
    image: "ghcr.io/daemonless/caddy:latest"
    state: started
    restart_policy: always
    env:
      TZ: "UTC"
    ports:
      - "80:80"
      - "443:443"
      - "443:443"
    volumes:
      - "/path/to/containers/caddy:/config"
      - "/path/to/containers/caddy/data:/data"

Save as caddy-deploy.yaml, then run ansible-playbook caddy-deploy.yaml.

Warning

Exposing ports in AppJail means that your service can be reached from remote hosts. If that is not your intention, do not expose the ports and communicate with the service using the jail's IPv4 address or hostname assigned by the virtual network.

1
2
3
4
# .env

DIRECTOR_PROJECT=caddy
TZ=UTC
# appjail-director.yml

options:
  - virtualnet: ':<random> default'
  - nat:
services:
  caddy:
    name: caddy
    options:
      - container: 'args:--pull'
      - expose: '80:80 proto:tcp'
      - expose: '443:443 proto:tcp'
      - expose: '443:443 proto:udp'
    oci:
      user: root
      environment:
        - TZ: !ENV '${TZ}'
    volumes:
      - CADDY_CONFIG_PATH: /config
      - CADDY_DATA_PATH: /data
volumes:
  CADDY_CONFIG_PATH:
    device: '/path/to/containers/caddy'
  CADDY_DATA_PATH:
    device: '/path/to/containers/caddy/data'
1
2
3
4
5
6
7
# Makejail

ARG tag=latest

OPTION container=boot
OPTION overwrite=force
OPTION from=ghcr.io/daemonless/caddy:${tag}

Save the files above, then run appjail-director up.

appjail oci run -Pd \
  -o overwrite=force \
  -o container="args:--pull" \
  -o virtualnet=":<random> default" \
  -o nat \
  -o expose="80:80 proto:tcp" \
  -o expose="443:443 proto:tcp" \
  -o expose="443:443 proto:udp" \
  -e TZ=UTC \
  -o fstab="/path/to/containers/caddy /config <pseudofs>" \
  -o fstab="/path/to/containers/caddy/data /data <pseudofs>" \
  ghcr.io/daemonless/caddy:latest caddy

Save the files above, then run sh run.sh.

Experimental

Bastille's OCI support is experimental. It requires buildah and shares the host network stack (inherit). Mount volumes with --volume HOST JAIL; without it, image-declared volumes are stored under ${bastille_volumesdir}/${jail}.

services:
  caddy:
    name: caddy
    image: "ghcr.io/daemonless/caddy:latest"
    network:
      - mode: host
    environment:
      - TZ=UTC
    volumes:
      - "/path/to/containers/caddy:/config"
      - "/path/to/containers/caddy/data:/data"

Save as bastille-compose.yml, then run bastille up.

1
2
3
4
5
bastille create -O \
  --env TZ=UTC \
  --volume /path/to/containers/caddy /config \
  --volume /path/to/containers/caddy/data /data \
  caddy ghcr.io/daemonless/caddy:latest inherit

Access at: http://localhost:80

Interactive Configuration

Parameters

Environment Variables

Variable Default Description
TZ UTC Timezone for the container

Volumes

Path Description
/config Configuration directory (Caddyfile)
/data Persistent data (ACME certificates, OCSP staples)

Ports

Port Protocol Description
80 TCP HTTP
443 TCP HTTPS (TCP + UDP/HTTP-3)
443 UDP HTTPS (TCP + UDP/HTTP-3)

Implementation Details

  • Architectures: amd64, aarch64
  • User: root (UID/GID set via PUID/PGID). Defaults to 1000:1000.
  • Base: Built on ghcr.io/daemonless/base (FreeBSD 15.1).

Need help? Join our Discord community.