1
0
Fork 0

Remove obsolete version field in compose files

This commit is contained in:
Thomas Mauran 2025-05-28 17:16:08 +02:00 committed by GitHub
parent 6a54f1f66c
commit 0b4058dde0
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
48 changed files with 0 additions and 80 deletions

View file

@ -15,8 +15,6 @@ A Use Case Using Docker
Create a `docker-compose.yml` file where you will define a `reverse-proxy` service that uses the official Traefik image:
```yaml
version: '3'
services:
reverse-proxy:
# The official v3 Traefik docker image
@ -50,8 +48,6 @@ Now that you have a Traefik instance up and running, you will deploy new service
Edit your `docker-compose.yml` file and add the following at the end of your file.
```yaml
version: '3'
services:
...

View file

@ -288,8 +288,6 @@ It is possible to configure the Traefik to timestamp in a specific timezone by e
Example utilizing Docker Compose:
```yaml
version: "3.7"
services:
traefik:
image: traefik:v3.4

View file

@ -40,7 +40,6 @@ This provider works with [Docker (standalone) Engine](https://docs.docker.com/en
Attaching labels to containers (in your docker compose file)
```yaml
version: "3"
services:
my-container:
# ...
@ -162,8 +161,6 @@ See the [Docker API Access](#docker-api-access) section for more information.
The docker-compose file shares the docker sock with the Traefik container
```yaml
version: '3'
services:
traefik:
image: traefik:v3.4 # The official v3 Traefik docker image

View file

@ -53,7 +53,6 @@ This provider works with [Docker Swarm Mode](https://docs.docker.com/engine/swar
then that service is automatically assigned to the router.
```yaml
version: "3"
services:
my-container:
deploy:
@ -176,8 +175,6 @@ docker service create \
```
```yml tab="With Docker Compose"
version: '3'
services:
traefik:
# ...
@ -208,8 +205,6 @@ See the [Docker Swarm API Access](#docker-api-access) section for more informati
The docker-compose file shares the docker sock with the Traefik container
```yaml
version: '3'
services:
traefik:
image: traefik:v3.4 # The official v3 Traefik docker image

View file

@ -199,8 +199,6 @@ It is possible to configure the Traefik to timestamp in a specific timezone by e
Example utilizing Docker Compose:
```yaml
version: "3.7"
services:
traefik:
image: traefik:v3.4

View file

@ -29,7 +29,6 @@ providers:
Attach labels to containers (in your Docker compose file)
```yaml
version: "3"
services:
my-container:
# ...
@ -67,8 +66,6 @@ See the [Docker API Access](#docker-api-access) section for more information.
The docker-compose file shares the docker sock with the Traefik container
```yaml
version: '3'
services:
traefik:
image: traefik:v3.1 # The official v3 Traefik docker image

View file

@ -33,7 +33,6 @@ When there is only one service, and the router does not specify a service,
then that service is automatically assigned to the router.
```yaml tab="Labels"
version: "3"
services:
my-container:
deploy:
@ -73,8 +72,6 @@ See the [Docker Swarm API Access](#docker-api-access) section for more informati
The docker-compose file shares the docker sock with the Traefik container
```yaml
version: '3'
services:
traefik:
image: traefik:v3.1 # The official v3 Traefik docker image
@ -405,8 +402,6 @@ docker service create \
```
```yml tab="With Docker Compose"
version: '3'
services:
traefik:
# ...

View file

@ -72,8 +72,6 @@ When using Docker or Amazon ECS, you can define routing configuration using cont
When deploying a Docker container, you can specify labels to define routing rules and services:
```yaml
version: '3'
services:
my-service:
image: my-image

View file

@ -35,7 +35,6 @@ With Docker, Traefik can leverage labels attached to a container to generate rou
Attaching labels to containers (in your docker compose file)
```yaml
version: "3"
services:
my-container:
# ...
@ -48,7 +47,6 @@ With Docker, Traefik can leverage labels attached to a container to generate rou
Forward requests for `http://example.com` to `http://<private IP of container>:12345`:
```yaml
version: "3"
services:
my-container:
# ...
@ -71,7 +69,6 @@ With Docker, Traefik can leverage labels attached to a container to generate rou
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:
# ...

View file

@ -48,7 +48,6 @@ With Docker Swarm, Traefik can leverage labels attached to a service to generate
then that service is automatically assigned to the router.
```yaml
version: "3"
services:
my-container:
deploy:
@ -67,7 +66,6 @@ With Docker Swarm, Traefik can leverage labels attached to a service to generate
Forward requests for `http://example.com` to `http://<private IP of container>:12345`:
```yaml
version: "3"
services:
my-container:
# ...
@ -93,7 +91,6 @@ With Docker Swarm, Traefik can leverage labels attached to a service to generate
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:
# ...

View file

@ -42,7 +42,6 @@ With Docker, Traefik can leverage labels attached to a container to generate rou
Attaching labels to containers (in your docker compose file)
```yaml
version: "3"
services:
my-container:
# ...
@ -55,7 +54,6 @@ With Docker, Traefik can leverage labels attached to a container to generate rou
Forward requests for `http://example.com` to `http://<private IP of container>:12345`:
```yaml
version: "3"
services:
my-container:
# ...
@ -78,7 +76,6 @@ With Docker, Traefik can leverage labels attached to a container to generate rou
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:
# ...

View file

@ -55,7 +55,6 @@ With Docker Swarm, Traefik can leverage labels attached to a service to generate
then that service is automatically assigned to the router.
```yaml
version: "3"
services:
my-container:
deploy:
@ -74,7 +73,6 @@ With Docker Swarm, Traefik can leverage labels attached to a service to generate
Forward requests for `http://example.com` to `http://<private IP of container>:12345`:
```yaml
version: "3"
services:
my-container:
# ...
@ -100,7 +98,6 @@ With Docker Swarm, Traefik can leverage labels attached to a service to generate
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:
# ...

View file

@ -1,5 +1,3 @@
version: "3.3"
services:
traefik:

View file

@ -1,5 +1,3 @@
version: "3.3"
secrets:
ovh_endpoint:
file: "./secrets/ovh_endpoint.secret"

View file

@ -1,5 +1,3 @@
version: "3.3"
services:
traefik:

View file

@ -1,5 +1,3 @@
version: "3.3"
services:
traefik:

View file

@ -1,5 +1,3 @@
version: "3.3"
services:
traefik:

View file

@ -23,8 +23,6 @@ Create a `docker-compose.yml` file with the following content:
You can use a [pre-existing network](https://docs.docker.com/compose/networking/#use-a-pre-existing-network "Link to Docker Compose networking docs") too.
```yaml
version: "3.3"
networks:
traefiknet: {}

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
server0:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
noOverrideAllowlist:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami1:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
consul:
image: consul:1.6

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
consul:
image: consul:1.6.2

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
simple:
image: swarm:1.0.0

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
nginx1:
image: nginx:1.25.3-alpine3.18

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
etcd:
image: quay.io/coreos/etcd:v3.5.14

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami1:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami1:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
server1:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
server:
image: rancher/k3s:v1.21.14-k3s1

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami1:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
pebble:
image: letsencrypt/pebble:v2.3.1

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami1:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
redis:
image: redis:5.0

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
master:
image: redis

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami1:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami1:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
tailscaled:
hostname: traefik-tests-gw # This will become the tailscale device name

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami-a:
image: traefik/whoamitcp

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
timeoutEndpoint:
image: yaman/timeout

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
tempo:
hostname: tempo

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
whoami-a:
image: traefik/whoamiudp:latest

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
noOverrideWhitelist:
image: traefik/whoami

View file

@ -1,4 +1,3 @@
version: "3.8"
services:
zookeeper:
image: zookeeper:3.5