quick-traefik

Locating functional Docker Compose service configurations for the Traefik reverse proxy can be a challenging quest, especially ones that encompass a fully operational Traefik dashboard, seamless integration with Let's Encrypt, and robust IPv6 support. The ever-evolving landscape of Traefik, coupled with configuration variations across different versions, further complicates this pursuit. Fear not! Below unfolds a comprehensive example tailored for the latest Traefik version available at the time of this writing.

This Docker Compose service configuration features:

• Forcefully nudges insecure requests towards the safer realms of HTTPS.
• Elevates the Traefik dashboard to its majestic throne, guarded by the impenetrable shield of basic authentication (credentials: traefik/traefik).
• Harnesses the power of the Let's Encrypt ACME TLS challenge to effortlessly summon certificates for your esteemed domains.
• Optionally embraces the futuristic realm of IPv6 support, allowing your Docker Compose service configuration to seamlessly communicate over the latest generation of Internet Protocol.

Usage

1. Edit .env to set configuration details
2. Create the required traefik network
3. Start the container with docker compose up -d
4. Monitor for errors with docker compose logs -f
5. Open your FQDNs in the browser and observe Traefik issuing certificates using Let's Encrypt's TLS challenge mechanism (may take a few seconds!).

Don't forget to remove the Let's Encrypt staging configuration in compose.yml once everything is ready!

Create the network bridge

Create a network bridge by following these steps:

1. For IPv4-only setups, use the command: docker network create traefik and you're done here.
2. If you want Traefik to be reachable over IPv6 too, modify the Docker daemon configuration in /etc/docker/daemon.json (example provided for Debian Bookworm):

{
  "ipv6": true,
  "ip6tables": true,
  "fixed-cidr-v6": "fd00:1::/64",
  "experimental": true
}

1. Restart the Docker daemon after making this configuration change.
2. Once the Docker daemon is restarted, initiate the IPv6-capable network bridge with the command: docker network create --ipv6 --subnet=fd00:2::/64 traefik