Skip to content

Commit 8f1150e

Browse files
authored
ENGDOCS-2079 (#19939)
* ENGDOCS-2079 * Fix links * Fix links * Fix links * Fix links
1 parent feaf1d0 commit 8f1150e

File tree

15 files changed

+28
-5480
lines changed

15 files changed

+28
-5480
lines changed

content/compose/compose-file/compose-file-v2.md

Lines changed: 0 additions & 1988 deletions
This file was deleted.

content/compose/compose-file/compose-file-v3.md

Lines changed: 0 additions & 2764 deletions
This file was deleted.

content/compose/compose-file/compose-versioning.md

Lines changed: 0 additions & 535 deletions
This file was deleted.
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Legacy versions
3+
description:
4+
keywords: fig, composition, compose, versions, upgrading, docker, version 3, docker compose 3
5+
aliases:
6+
- /compose/compose-file/compose-versioning/
7+
- /compose/compose-file/compose-file-v3/
8+
- /compose/compose-file/compose-file-v2/
9+
---
10+
11+
The legacy versions of the Compose file reference has moved to the [V1 branch of the Compose repository](https://github.com/docker/compose/tree/v1/docs). They are no longer being actively maintained.
12+
13+
The latest and recommended version of the Compose file format is defined by the [Compose Specification](_index.md). This format merges the 2.x and 3.x versions and is implemented by **Compose 1.27.0+**. For more information, see the[History and development of Docker Compose](../intro/history.md).

content/compose/intro/history.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,9 @@ Compose V2 ignores the `version` top-level element in the `compose.yml` file.
3434
The Docker Compose CLIs are defined by specific file formats.
3535

3636
Three major versions of the Compose file format for Compose V1 were released:
37-
- [Compose file format 1](../compose-file/compose-versioning.md##version-1-to-2x) with Compose 1.0.0 in 2014
38-
- [Compose file format 2.x](../compose-file/compose-file-v2.md) with Compose 1.6.0 in 2016
39-
- [Compose file format 3.x](../compose-file/compose-file-v3.md) with Compose 1.10.0 in 2017
37+
- Compose file format 1 with Compose 1.0.0 in 2014
38+
- Compose file format 2.x with Compose 1.6.0 in 2016
39+
- Compose file format 3.x with Compose 1.10.0 in 2017
4040

4141
Compose file format 1 is substantially different to all the following formats as it lacks a top-level `services` key.
4242
Its usage is historical and files written in this format don't run with Compose V2.

content/compose/release-notes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2209,7 +2209,7 @@ naming scheme accordingly before upgrading.
22092209

22102210
- Added support for `extra_hosts` in build configuration
22112211

2212-
- Added support for the [long syntax](compose-file/compose-file-v3.md#long-syntax-3) for volume entries, as previously introduced in the 3.2 format.
2212+
- Added support for the [long syntax](compose-file/legacy-versions.md) for volume entries, as previously introduced in the 3.2 format.
22132213
Using this syntax will create [mounts](../storage/bind-mounts.md) instead of volumes.
22142214

22152215
#### Compose file version 2.1 and up
@@ -3145,7 +3145,7 @@ naming scheme accordingly before upgrading.
31453145
You don't have to use it - your existing Compose files will run on Compose
31463146
1.6 exactly as they do today.
31473147

3148-
Check the [upgrade guide](../compose/compose-file/compose-versioning.md#upgrading)
3148+
Check the [upgrade guide](../compose/compose-file/legacy-versions.md)
31493149
for full details.
31503150

31513151
- Support for networking has exited experimental status and is the recommended

content/engine/swarm/configs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ Docker configs.
133133

134134
The `docker stack` command supports defining configs in a Compose file.
135135
However, the `configs` key is not supported for `docker compose`. See
136-
[the Compose file reference](../../compose/compose-file/compose-file-v3.md#configs) for details.
136+
[the Compose file reference](../../compose/compose-file/legacy-versions.md) for details.
137137

138138
### Simple example: Get started with configs
139139

content/engine/swarm/secrets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ a similar way, see
143143

144144
Both the `docker-compose` and `docker stack` commands support defining secrets
145145
in a compose file. See
146-
[the Compose file reference](../../compose/compose-file/compose-file-v3.md#secrets) for details.
146+
[the Compose file reference](../../compose/compose-file/legacy-versions.md) for details.
147147

148148
### Simple example: Get started with secrets
149149

content/engine/swarm/stack-deploy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ title: Deploy a stack to a swarm
66

77
When running Docker Engine in swarm mode, you can use `docker stack deploy` to
88
deploy a complete application stack to the swarm. The `deploy` command accepts
9-
a stack description in the form of a [Compose file](../../compose/compose-file/compose-file-v3.md).
9+
a stack description in the form of a [Compose file](../../compose/compose-file/legacy-versions.md).
1010

1111
{{< include "swarm-compose-compat.md" >}}
1212

content/includes/content/compose-extfields-sub.md

Lines changed: 0 additions & 77 deletions
This file was deleted.

0 commit comments

Comments
 (0)