haaev.blogg.se

The server starts without any configuration, and will not serve anything until it is configured by a "controller".

ServerĪcts as a proxy to your Docker resources. Chosing between default or alpine imagesīasic usage example, using docker-compose $ docker network create caddyĬaddy/docker-compose.yml version: "3.7" services: caddy: image: lucaslorentz/caddy-docker-proxy:ci-alpine ports: - 80 :80 - 443 :443 environment: - CADDY_INGRESS_NETWORKS=caddy networks: - caddy volumes: - /var/run/docker.sock:/var/run/docker.sock - caddy_data:/data restart: unless-stopped networks: caddy: external: true volumes: caddy_data: Execution modesĮach caddy docker proxy instance can be executed in one of the following modes.Basic usage example, using docker-compose.Then, it generates an in-memory Caddyfile with site entries and proxies pointing to each Docker service by their DNS name or container IP.Įvery time a Docker object changes, the plugin updates the Caddyfile and triggers Caddy to gracefully reload, with zero-downtime.

The plugin scans Docker metadata, looking for labels indicating that the service or container should be served by Caddy. This plugin enables Caddy to be used as a reverse proxy for Docker containers via labels.