1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
docker-compose (2.32.4-2) experimental; urgency=medium
* A local ".env" file can now be used to override "COMPOSE_*" environment
variables.
* Added the ability to use Docker Buildx Bake to build Compose services.
* Compose now recreates containers when the volume or network configuration
changes.
-- Nicolas Peugnet <nicolas@club1.fr> Tue, 21 Oct 2025 11:30:47 +0200
docker-compose (2.26.1-4) unstable; urgency=medium
Unlike Compose V1, Compose V2 integrates into the Docker CLI platform and
the recommended command-line syntax is "docker compose".
The previous behaviour is still supported, but it is recommended that you
adapt to the new preferred way of running Compose V2, which is to use
"docker compose" instead of "docker-compose".
Compose generates container names based on the project name, service name,
and scale/replica count.
In Compose V1, an underscore (_) was used as the word separator. In Compose
V2, a hyphen (-) is used as the word separator.
The global "--compatibility" flag or "COMPOSE_COMPATIBILITY" environment
variable preserves the Compose V1 behavior to use underscores (_) as the
word separator.
-- Nicolas Peugnet <nicolas@club1.fr> Sun, 09 Feb 2025 17:35:45 +0100
docker-compose (1.5.1-1) unstable; urgency=medium
With the introduction of variable substitution support in the Compose file,
any Compose file that uses an environment variable ($VAR or ${VAR}) in the
command or entrypoint fields will break.
Please see the 1.5.0 version section of
/usr/share/doc/docker-compose/changelog.gz for details
-- Felipe Sateler <fsateler@debian.org> Sat, 14 Nov 2015 15:15:38 -0300
docker-compose (1.3.1-1) unstable; urgency=medium
Compose since version 1.3.0 now uses labels to identify containers. This
means that containers created by older versions are incompatible with newer
ones, and that the daemon has to be at least version 1.6.0.
Compose will refuse to start containers where it detects that they were
created with older versions.
Please see the Upgrading section of /usr/share/doc/docker-compose/install.md
for instructions on upgrading your containers.
-- Felipe Sateler <fsateler@debian.org> Sun, 28 Jun 2015 00:24:29 -0300
|
