Docker Compose example

In this section, you will learn how to use Docker Compose to expose a service using the Docker provider.

Setup

Create a docker-compose.yml file with the following content:

  1. version: "3.3"
  3. services:
  5.   traefik:
  6.     image: "traefik:v3.2"
  7.     container_name: "traefik"
  8.     command:
  9.       #- "--log.level=DEBUG"
  10.       - "--api.insecure=true"
  11.       - "--providers.docker=true"
  12.       - "--providers.docker.exposedbydefault=false"
  13.       - "--entryPoints.web.address=:80"
  14.     ports:
  15.       - "80:80"
  16.       - "8080:8080"
  17.     volumes:
  18.       - "/var/run/docker.sock:/var/run/docker.sock:ro"
  20.   whoami:
  21.     image: "traefik/whoami"
  22.     container_name: "simple-service"
  23.     labels:
  24.       - "traefik.enable=true"
  25.       - "traefik.http.routers.whoami.rule=Host(`whoami.localhost`)"
  26.       - "traefik.http.routers.whoami.entrypoints=web"

Networking

The Traefik container has to be attached to the same network as the containers to be exposed. If no networks are specified in the Docker Compose file, Docker creates a default one that allows Traefik to reach the containers defined in the same file. You can customize the network as described in the example below. You can use a pre-existing network too.

  1. version: "3.3"
  3. networks:
  4.   traefiknet: {}
  6. services:
  8.   traefik:
  9.     image: "traefik:v3.2"
  10.     ...
  11.     networks:
  12.       - traefiknet
  14.   whoami:
  15.     image: "traefik/whoami"
  16.     ...
  17.     networks:
  18.       - traefiknet

Replace whoami.localhost by your own domain within the traefik.http.routers.whoami.rule label of the whoami service.

Now run docker-compose up -d within the folder where you created the previous file.
This will start Docker Compose in background mode.

This can take a moment

Docker Compose will now create and start the services declared in the docker-compose.yml.

Wait a bit and visit http://your_own_domain to confirm everything went fine.

You should see the output of the whoami service.
It should be similar to the following example:

  1. Hostname: d7f919e54651
  2. IP: 127.0.0.1
  3. IP: 192.168.64.2
  4. GET / HTTP/1.1
  5. Host: whoami.localhost
  6. User-Agent: curl/7.52.1
  7. Accept: */*
  8. Accept-Encoding: gzip
  9. X-Forwarded-For: 192.168.64.1
  10. X-Forwarded-Host: whoami.localhost
  11. X-Forwarded-Port: 80
  12. X-Forwarded-Proto: http
  13. X-Forwarded-Server: 7f0c797dbc51
  14. X-Real-Ip: 192.168.64.1

Details

Let’s break it down and go through it, step-by-step.

You use whoami, a tiny Go server that prints OS information and HTTP request to output as service container.

Second, you define an entry point, along with the exposure of the matching port within Docker Compose, which allows to “open and accept” HTTP traffic:

  1. command:
  2.   # Traefik will listen to incoming request on the port 80 (HTTP)
  3.   - "--entryPoints.web.address=:80"
  5. ports:
  6.   - "80:80"

Third, you expose the Traefik API to be able to check the configuration if needed:

  1. command:
  2.   # Traefik will listen on port 8080 by default for API request.
  3.   - "--api.insecure=true"
  5. ports:
  6.   - "8080:8080"

Note

If you are working on a remote server, you can use the following command to display configuration (require curl & jq):

  1. curl -s 127.0.0.1:8080/api/rawdata | jq .

Fourth, you allow Traefik to gather configuration from Docker:

  1. traefik:
  2.   command:
  3.     # Enabling Docker provider
  4.     - "--providers.docker=true"
  5.     # Do not expose containers unless explicitly told so
  6.     - "--providers.docker.exposedbydefault=false"
  7.   volumes:
  8.     - "/var/run/docker.sock:/var/run/docker.sock:ro"
  10. whoami:
  11.   labels:
  12.     # Explicitly tell Traefik to expose this container
  13.     - "traefik.enable=true"
  14.     # The domain the service will respond to
  15.     - "traefik.http.routers.whoami.rule=Host(`whoami.localhost`)"
  16.     # Allow request only from the predefined entry point named "web"
  17.     - "traefik.http.routers.whoami.entrypoints=web"

Using Traefik OSS in Production?

If you are using Traefik at work, consider adding enterprise-grade API gateway capabilities or commercial support for Traefik OSS.

Adding API Gateway capabilities to Traefik OSS is fast and seamless. There’s no rip and replace and all configurations remain intact. See it in action via this short video.