This is based Traefik v1.7. It's important because 2.0 made breaking changes to syntax of toml file and docker labels.
I reconfigured traefik for:
You don't need to create traefik.toml file. Just create docker-compose.yml and You are good to go.
This container is configured for simplicity. Because of that, default SSL keys are generated in Dockerfile and they can be extracted and used to decrypt ssl communication. They should be treated as leaked/not secure.
When using it for development or staging responsibly it should not matter. If used behind cloudflare.com it helps a bit, but still insecure.
If traefik succeeds at generating letsencrypt certificate, this warning does not apply.
You can insert Your own default certificate keys at /opt/traefik/certs/.
version: '2'
services:
reverse-proxy:
image: ipepe/traefik
restart: always
network_mode: bridge
command: --acme.email="[email protected]"
ports:
- "80:80"
- "443:443"
- "8080:8080"
volumes:
- /var/run/docker.sock:/var/run/docker.sock # So that Traefik can listen to the Docker events
version: '2'
services:
swagger-editor:
image: swaggerapi/swagger-editor
restart: always
network_mode: bridge
expose:
- '8080'
labels:
- 'traefik.enable=true'
- 'traefik.port=8080'
- 'traefik.frontend.rule=Host:swagger.example.org,secondhost.example.org'
Content type
Image
Digest
sha256:fe383efbb…
Size
24.5 MB
Last updated
about 2 years ago
docker pull ipepe/traefik