traefik/docs/content/routing/providers/docker.md

642 lines
20 KiB
Markdown
Raw Normal View History

2019-09-23 12:32:04 +00:00
# Traefik & Docker
A Story of Labels & Containers
{: .subtitle }
![Docker](../../assets/img/providers/docker.png)
Attach labels to your containers and let Traefik do the rest!
## Configuration Examples
??? example "Configuring Docker & Deploying / Exposing Services"
Enabling the docker provider
2019-09-23 12:32:04 +00:00
```toml tab="File (TOML)"
[providers.docker]
```
2019-09-23 12:32:04 +00:00
```yaml tab="File (YAML)"
providers:
docker: {}
```
2019-09-23 12:32:04 +00:00
```bash tab="CLI"
--providers.docker=true
```
Attaching labels to containers (in your docker compose file)
```yaml
version: "3"
services:
my-container:
# ...
labels:
2020-03-13 21:50:05 +00:00
- traefik.http.routers.my-container.rule=Host(`example.com`)
2019-09-23 12:32:04 +00:00
```
??? example "Specify a Custom Port for the Container"
2020-03-13 21:50:05 +00:00
Forward requests for `http://example.com` to `http://<private IP of container>:12345`:
```yaml
version: "3"
services:
my-container:
# ...
labels:
2020-03-13 21:50:05 +00:00
- traefik.http.routers.my-container.rule=Host(`example.com`)
# Tell Traefik to use the port 12345 to connect to `my-container`
- traefik.http.services.my-service.loadbalancer.server.port=12345
```
!!! important "Traefik Connecting to the Wrong Port: `HTTP/502 Gateway Error`"
By default, Traefik uses the first exposed port of a container.
Setting the label `traefik.http.services.xxx.loadbalancer.server.port`
overrides that behavior.
??? example "Specifying more than one router and service per container"
Forwarding requests to more than one port on a container requires referencing the service loadbalancer port definition using the service parameter on the router.
In this example, requests are forwarded for `http://example-a.com` to `http://<private IP of container>:8000` in addition to `http://example-b.com` forwarding to `http://<private IP of container>:9000`:
```yaml
version: "3"
services:
my-container:
# ...
labels:
- traefik.http.routers.www-router.rule=Host(`example-a.com`)
- traefik.http.routers.www-router.service=www-service
- traefik.http.services.www-service.loadbalancer.server.port=8000
- traefik.http.routers.admin-router.rule=Host(`example-b.com`)
- traefik.http.routers.admin-router.service=admin-service
- traefik.http.services.admin-service.loadbalancer.server.port=9000
```
2019-09-23 12:32:04 +00:00
??? example "Configuring Docker Swarm & Deploying / Exposing Services"
Enabling the docker provider (Swarm Mode)
```toml tab="File (TOML)"
[providers.docker]
# swarm classic (1.12-)
# endpoint = "tcp://127.0.0.1:2375"
# docker swarm mode (1.12+)
endpoint = "tcp://127.0.0.1:2377"
swarmMode = true
```
2019-09-23 12:32:04 +00:00
```yaml tab="File (YAML)"
providers:
docker:
# swarm classic (1.12-)
2020-09-23 09:38:03 +00:00
# endpoint: "tcp://127.0.0.1:2375"
2019-09-23 12:32:04 +00:00
# docker swarm mode (1.12+)
2020-09-23 09:38:03 +00:00
endpoint: "tcp://127.0.0.1:2377"
2019-09-23 12:32:04 +00:00
swarmMode: true
```
2019-09-23 12:32:04 +00:00
```bash tab="CLI"
2020-09-23 09:38:03 +00:00
# swarm classic (1.12-)
# --providers.docker.endpoint=tcp://127.0.0.1:2375
# docker swarm mode (1.12+)
--providers.docker.endpoint=tcp://127.0.0.1:2377
2019-09-23 12:32:04 +00:00
--providers.docker.swarmMode=true
```
Attach labels to services (not to containers) while in Swarm mode (in your docker compose file)
```yaml
version: "3"
services:
my-container:
deploy:
labels:
2020-03-13 21:50:05 +00:00
- traefik.http.routers.my-container.rule=Host(`example.com`)
2019-09-23 12:32:04 +00:00
- traefik.http.services.my-container-service.loadbalancer.server.port=8080
```
!!! important "Labels in Docker Swarm Mode"
While in Swarm Mode, Traefik uses labels found on services, not on individual containers.
Therefore, if you use a compose file with Swarm Mode, labels should be defined in the `deploy` part of your service.
This behavior is only enabled for docker-compose version 3+ ([Compose file reference](https://docs.docker.com/compose/compose-file/#labels-1)).
## Routing Configuration
!!! info "Labels"
2019-09-23 12:32:04 +00:00
- Labels are case insensitive.
- The complete list of labels can be found in [the reference page](../../reference/dynamic-configuration/docker.md).
2019-09-23 12:32:04 +00:00
### General
Traefik creates, for each container, a corresponding [service](../services/index.md) and [router](../routers/index.md).
The Service automatically gets a server per instance of the container,
and the router automatically gets a rule defined by `defaultRule` (if no rule for it was defined in labels).
#### Service definition
--8<-- "content/routing/providers/service-by-label.md"
??? example "Automatic service assignment with labels"
With labels in a compose file
```yaml
labels:
2020-03-13 21:50:05 +00:00
- "traefik.http.routers.myproxy.rule=Host(`example.net`)"
# service myservice gets automatically assigned to router myproxy
- "traefik.http.services.myservice.loadbalancer.server.port=80"
```
??? example "Automatic service creation and assignment with labels"
With labels in a compose file
```yaml
labels:
# no service specified or defined and yet one gets automatically created
# and assigned to router myproxy.
2020-03-13 21:50:05 +00:00
- "traefik.http.routers.myproxy.rule=Host(`example.net`)"
```
2019-09-23 12:32:04 +00:00
### Routers
To update the configuration of the Router automatically attached to the container,
add labels starting with `traefik.http.routers.<name-of-your-choice>.` and followed by the option you want to change.
2020-03-13 21:50:05 +00:00
For example, to change the rule, you could add the label ```traefik.http.routers.my-container.rule=Host(`example.com`)```.
2019-09-23 12:32:04 +00:00
!!! warning "The character `@` is not authorized in the router name `<router_name>`."
2019-09-23 12:32:04 +00:00
??? info "`traefik.http.routers.<router_name>.rule`"
See [rule](../routers/index.md#rule) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2020-03-13 21:50:05 +00:00
- "traefik.http.routers.myrouter.rule=Host(`example.com`)"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.http.routers.<router_name>.entrypoints`"
See [entry points](../routers/index.md#entrypoints) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2019-11-27 19:08:03 +00:00
- "traefik.http.routers.myrouter.entrypoints=ep1,ep2"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.http.routers.<router_name>.middlewares`"
See [middlewares](../routers/index.md#middlewares) and [middlewares overview](../../middlewares/overview.md) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.routers.myrouter.middlewares=auth,prefix,cb"
```
??? info "`traefik.http.routers.<router_name>.service`"
See [service](../routers/index.md#service) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.routers.myrouter.service=myservice"
```
??? info "`traefik.http.routers.<router_name>.tls`"
2019-09-23 12:32:04 +00:00
See [tls](../routers/index.md#tls) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.routers.myrouter.tls=true"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.http.routers.<router_name>.tls.certresolver`"
2019-09-23 12:32:04 +00:00
See [certResolver](../routers/index.md#certresolver) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.routers.myrouter.tls.certresolver=myresolver"
```
??? info "`traefik.http.routers.<router_name>.tls.domains[n].main`"
2019-09-23 12:32:04 +00:00
See [domains](../routers/index.md#domains) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2020-03-13 21:50:05 +00:00
- "traefik.http.routers.myrouter.tls.domains[0].main=example.org"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.http.routers.<router_name>.tls.domains[n].sans`"
2019-09-23 12:32:04 +00:00
See [domains](../routers/index.md#domains) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2020-03-13 21:50:05 +00:00
- "traefik.http.routers.myrouter.tls.domains[0].sans=test.example.org,dev.example.org"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.http.routers.<router_name>.tls.options`"
2019-09-23 12:32:04 +00:00
See [options](../routers/index.md#options) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.routers.myrouter.tls.options=foobar"
```
??? info "`traefik.http.routers.<router_name>.priority`"
See [priority](../routers/index.md#priority) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.routers.myrouter.priority=42"
```
### Services
To update the configuration of the Service automatically attached to the container,
add labels starting with `traefik.http.services.<name-of-your-choice>.`, followed by the option you want to change.
For example, to change the `passHostHeader` behavior,
you'd add the label `traefik.http.services.<name-of-your-choice>.loadbalancer.passhostheader=false`.
!!! warning "The character `@` is not authorized in the service name `<service_name>`."
2019-09-23 12:32:04 +00:00
??? info "`traefik.http.services.<service_name>.loadbalancer.server.port`"
2019-09-23 12:32:04 +00:00
Registers a port.
Useful when the container exposes multiples ports.
Mandatory for Docker Swarm (see the section ["Port Detection with Docker Swarm"](../../providers/docker.md#port-detection_1)).
{: #port }
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.server.port=8080"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.server.scheme`"
2019-09-23 12:32:04 +00:00
Overrides the default scheme.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.server.scheme=http"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.passhostheader`"
See [pass Host header](../services/index.md#pass-host-header) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.passhostheader=true"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.healthcheck.headers.<header_name>`"
2019-09-23 12:32:04 +00:00
See [health check](../services/index.md#health-check) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.healthcheck.headers.X-Foo=foobar"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.healthcheck.hostname`"
2019-09-23 12:32:04 +00:00
See [health check](../services/index.md#health-check) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2020-03-13 21:50:05 +00:00
- "traefik.http.services.myservice.loadbalancer.healthcheck.hostname=example.org"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.http.services.<service_name>.loadbalancer.healthcheck.interval`"
2019-09-23 12:32:04 +00:00
See [health check](../services/index.md#health-check) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2020-05-26 19:54:03 +00:00
- "traefik.http.services.myservice.loadbalancer.healthcheck.interval=10s"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.http.services.<service_name>.loadbalancer.healthcheck.path`"
2019-09-23 12:32:04 +00:00
See [health check](../services/index.md#health-check) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.healthcheck.path=/foo"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.healthcheck.port`"
2019-09-23 12:32:04 +00:00
See [health check](../services/index.md#health-check) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.healthcheck.port=42"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.healthcheck.scheme`"
2019-09-23 12:32:04 +00:00
See [health check](../services/index.md#health-check) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.healthcheck.scheme=http"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.healthcheck.timeout`"
2019-09-23 12:32:04 +00:00
See [health check](../services/index.md#health-check) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.healthcheck.timeout=10"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.healthcheck.followredirects`"
See [health check](../services/index.md#health-check) for more information.
```yaml
- "traefik.http.services.myservice.loadbalancer.healthcheck.followredirects=true"
```
2020-04-29 15:10:05 +00:00
??? info "`traefik.http.services.<service_name>.loadbalancer.sticky.cookie`"
2019-09-23 12:32:04 +00:00
See [sticky sessions](../services/index.md#sticky-sessions) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2020-04-29 15:10:05 +00:00
- "traefik.http.services.myservice.loadbalancer.sticky.cookie=true"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.http.services.<service_name>.loadbalancer.sticky.cookie.httponly`"
2019-09-23 12:32:04 +00:00
See [sticky sessions](../services/index.md#sticky-sessions) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.sticky.cookie.httponly=true"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.sticky.cookie.name`"
2019-09-23 12:32:04 +00:00
See [sticky sessions](../services/index.md#sticky-sessions) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.sticky.cookie.name=foobar"
```
??? info "`traefik.http.services.<service_name>.loadbalancer.sticky.cookie.secure`"
2019-09-23 12:32:04 +00:00
See [sticky sessions](../services/index.md#sticky-sessions) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.sticky.cookie.secure=true"
```
2020-03-23 10:24:05 +00:00
??? info "`traefik.http.services.<service_name>.loadbalancer.sticky.cookie.samesite`"
See [sticky sessions](../services/index.md#sticky-sessions) for more information.
```yaml
- "traefik.http.services.myservice.loadbalancer.sticky.cookie.samesite=none"
```
2019-09-23 12:32:04 +00:00
??? info "`traefik.http.services.<service_name>.loadbalancer.responseforwarding.flushinterval`"
See [response forwarding](../services/index.md#response-forwarding) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.http.services.myservice.loadbalancer.responseforwarding.flushinterval=10"
```
### Middleware
You can declare pieces of middleware using labels starting with `traefik.http.middlewares.<name-of-your-choice>.`,
followed by the middleware type/options.
For example, to declare a middleware [`redirectscheme`](../../middlewares/redirectscheme.md) named `my-redirect`,
you'd write `traefik.http.middlewares.my-redirect.redirectscheme.scheme=https`.
More information about available middlewares in the dedicated [middlewares section](../../middlewares/overview.md).
!!! warning "The character `@` is not authorized in the middleware name."
2019-09-23 12:32:04 +00:00
??? example "Declaring and Referencing a Middleware"
```yaml
services:
my-container:
# ...
labels:
# Declaring a middleware
- traefik.http.middlewares.my-redirect.redirectscheme.scheme=https
# Referencing a middleware
- traefik.http.routers.my-container.middlewares=my-redirect
```
!!! warning "Conflicts in Declaration"
If you declare multiple middleware with the same name but with different parameters, the middleware fails to be declared.
### TCP
You can declare TCP Routers and/or Services using labels.
??? example "Declaring TCP Routers and Services"
```yaml
services:
my-container:
# ...
labels:
2020-03-13 21:50:05 +00:00
- "traefik.tcp.routers.my-router.rule=HostSNI(`example.com`)"
2019-09-23 12:32:04 +00:00
- "traefik.tcp.routers.my-router.tls=true"
- "traefik.tcp.services.my-service.loadbalancer.server.port=4123"
```
!!! warning "TCP and HTTP"
If you declare a TCP Router/Service, it will prevent Traefik from automatically creating an HTTP Router/Service (like it does by default if no TCP Router/Service is defined).
You can declare both a TCP Router/Service and an HTTP Router/Service for the same container (but you have to do so manually).
#### TCP Routers
??? info "`traefik.tcp.routers.<router_name>.entrypoints`"
2019-09-23 12:32:04 +00:00
See [entry points](../routers/index.md#entrypoints_1) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.tcp.routers.mytcprouter.entrypoints=ep1,ep2"
```
??? info "`traefik.tcp.routers.<router_name>.rule`"
2019-09-23 12:32:04 +00:00
See [rule](../routers/index.md#rule_1) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2020-03-13 21:50:05 +00:00
- "traefik.tcp.routers.mytcprouter.rule=HostSNI(`example.com`)"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.tcp.routers.<router_name>.service`"
2019-09-23 12:32:04 +00:00
See [service](../routers/index.md#services) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.tcp.routers.mytcprouter.service=myservice"
```
??? info "`traefik.tcp.routers.<router_name>.tls`"
2019-09-23 12:32:04 +00:00
See [TLS](../routers/index.md#tls_1) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.tcp.routers.mytcprouter.tls=true"
```
??? info "`traefik.tcp.routers.<router_name>.tls.certresolver`"
2019-09-23 12:32:04 +00:00
See [certResolver](../routers/index.md#certresolver_1) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.tcp.routers.mytcprouter.tls.certresolver=myresolver"
```
??? info "`traefik.tcp.routers.<router_name>.tls.domains[n].main`"
2019-09-23 12:32:04 +00:00
See [domains](../routers/index.md#domains_1) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2020-03-13 21:50:05 +00:00
- "traefik.tcp.routers.mytcprouter.tls.domains[0].main=example.org"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.tcp.routers.<router_name>.tls.domains[n].sans`"
2019-09-23 12:32:04 +00:00
See [domains](../routers/index.md#domains_1) for more information.
2019-09-23 12:32:04 +00:00
```yaml
2020-03-13 21:50:05 +00:00
- "traefik.tcp.routers.mytcprouter.tls.domains[0].sans=test.example.org,dev.example.org"
2019-09-23 12:32:04 +00:00
```
??? info "`traefik.tcp.routers.<router_name>.tls.options`"
2019-09-23 12:32:04 +00:00
See [options](../routers/index.md#options_1) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.tcp.routers.mytcprouter.tls.options=mysoptions"
```
??? info "`traefik.tcp.routers.<router_name>.tls.passthrough`"
2019-09-23 12:32:04 +00:00
See [TLS](../routers/index.md#tls_1) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.tcp.routers.mytcprouter.tls.passthrough=true"
```
#### TCP Services
??? info "`traefik.tcp.services.<service_name>.loadbalancer.server.port`"
2019-09-23 12:32:04 +00:00
Registers a port of the application.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.tcp.services.mytcpservice.loadbalancer.server.port=423"
```
??? info "`traefik.tcp.services.<service_name>.loadbalancer.terminationdelay`"
2019-09-23 15:00:06 +00:00
See [termination delay](../services/index.md#termination-delay) for more information.
2019-09-23 12:32:04 +00:00
```yaml
- "traefik.tcp.services.mytcpservice.loadbalancer.terminationdelay=100"
```
??? info "`traefik.tcp.services.<service_name>.loadbalancer.proxyprotocol.version`"
See [PROXY protocol](../services/index.md#proxy-protocol) for more information.
```yaml
- "traefik.tcp.services.mytcpservice.loadbalancer.proxyprotocol.version=1"
```
2020-02-20 21:24:05 +00:00
### UDP
You can declare UDP Routers and/or Services using labels.
??? example "Declaring UDP Routers and Services"
```yaml
services:
my-container:
# ...
labels:
- "traefik.udp.routers.my-router.entrypoints=udp"
2020-02-20 21:24:05 +00:00
- "traefik.udp.services.my-service.loadbalancer.server.port=4123"
```
!!! warning "UDP and HTTP"
If you declare a UDP Router/Service, it will prevent Traefik from automatically creating an HTTP Router/Service (like it does by default if no UDP Router/Service is defined).
You can declare both a UDP Router/Service and an HTTP Router/Service for the same container (but you have to do so manually).
#### UDP Routers
??? info "`traefik.udp.routers.<router_name>.entrypoints`"
See [entry points](../routers/index.md#entrypoints_2) for more information.
```yaml
- "traefik.udp.routers.myudprouter.entrypoints=ep1,ep2"
```
??? info "`traefik.udp.routers.<router_name>.service`"
See [service](../routers/index.md#services_1) for more information.
```yaml
- "traefik.udp.routers.myudprouter.service=myservice"
```
#### UDP Services
??? info "`traefik.udp.services.<service_name>.loadbalancer.server.port`"
Registers a port of the application.
```yaml
- "traefik.udp.services.myudpservice.loadbalancer.server.port=423"
```
2019-09-23 12:32:04 +00:00
### Specific Provider Options
#### `traefik.enable`
```yaml
- "traefik.enable=true"
```
You can tell Traefik to consider (or not) the container by setting `traefik.enable` to true or false.
This option overrides the value of `exposedByDefault`.
#### `traefik.docker.network`
```yaml
- "traefik.docker.network=mynetwork"
```
Overrides the default docker network to use for connections to the container.
If a container is linked to several networks, be sure to set the proper network name (you can check this with `docker inspect <container_id>`),
otherwise it will randomly pick one (depending on how docker is returning them).
!!! warning
When deploying a stack from a compose file `stack`, the networks defined are prefixed with `stack`.
#### `traefik.docker.lbswarm`
```yaml
- "traefik.docker.lbswarm=true"
```
Enables Swarm's inbuilt load balancer (only relevant in Swarm Mode).
If you enable this option, Traefik will use the virtual IP provided by docker swarm instead of the containers IPs.
Which means that Traefik will not perform any kind of load balancing and will delegate this task to swarm.