Skip to content

Commit f69de11

Browse files
committed
Bump 1.2.0
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
1 parent 78227c3 commit f69de11

4 files changed

Lines changed: 50 additions & 3 deletions

File tree

CHANGES.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,53 @@
11
Change log
22
==========
33

4+
1.2.0rc3 (2015-01-01)
5+
---------------------
6+
7+
This is a release candidate for Compose 1.2.0.
8+
9+
On top of the changes listed below for RC1 and RC2, the following bugs have been fixed:
10+
11+
- When copying a service's configuration with `extends`, `image` and `build` could come into conflict, resulting in an error, as it makes no sense to have both defined. Each now overwrites the other: if a service with `image` defined is extended and `build` is added, the `image` entry will be removed.
12+
13+
- When copying a service's configuration with `extends`, if both services defined a multi-value option such as `ports` or `dns`, the original value would be completely discarded. They are now concatenated instead.
14+
15+
- When a relative path is supplied to `build`, it is treated as relative to the *directory of the configuration file*, not the directory that `docker-compose` is being run in. In the majority of cases, those are the same, but if you use the `-f|--file` argument to specify a configuration file in another directory, **this is a breaking change**.
16+
17+
1.2.0rc2 (2015-03-24)
18+
---------------------
19+
20+
This is a release candidate for Compose 1.2.0.
21+
22+
On top of the changes listed below for RC1, a bug has been fixed where containers were being created with blank entries for "Dns" and "DnsSearch", causing DNS lookups from within a container to fail.
23+
24+
1.2.0rc1 (2015-03-23)
25+
---------------------
26+
27+
This is a release candidate for Compose 1.2.0.
28+
29+
- `docker-compose.yml` now supports an `extends` option, which enables a service to inherit configuration from another service in another configuration file. This is really good for sharing common configuration between apps, or for configuring the same app for different environments. Here's the [documentation](https://github.com/docker/compose/blob/master/docs/yml.md#extends).
30+
31+
- When using Compose with a Swarm cluster, containers that depend on one another will be co-scheduled on the same node. This means that most Compose apps will now work out of the box, as long as they don't use `build`.
32+
33+
- Repeated invocations of `docker-compose up` when using Compose with a Swarm cluster now work reliably.
34+
35+
- Filenames in `env_file` and volume host paths in `volumes` are now treated as relative to the *directory of the configuration file*, not the directory that `docker-compose` is being run in. In the majority of cases, those are the same, but if you use the `-f|--file` argument to specify a configuration file in another directory, **this is a breaking change**.
36+
37+
- A service can now share another service's network namespace with `net: container:<service>`.
38+
39+
- `volumes_from` and `net: container:<service>` entries are taken into account when resolving dependencies, so `docker-compose up <service>` will correctly start all dependencies of `<service>`.
40+
41+
- Problems with authentication when using images from third-party registries have been fixed.
42+
43+
- `docker-compose run` now accepts a `--user` argument to specify a user to run the command as, just like `docker run`.
44+
45+
- The `up`, `stop` and `restart` commands now accept a `--timeout` (or `-t`) argument to specify how long to wait when attempting to gracefully stop containers, just like `docker stop`.
46+
47+
- `docker-compose rm` now accepts `-f` as a shorthand for `--force`, just like `docker rm`.
48+
49+
Thanks, @abesto, @albers, @alunduil, @dnephin, @funkyfuture, @gilclark, @IanVS, @KingsleyKelly, @knutwalker, @thaJeztah and @vmalloc!
50+
451
1.1.0 (2015-02-25)
552
------------------
653

compose/__init__.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
from __future__ import unicode_literals
22
from .service import Service # noqa:flake8
33

4-
__version__ = '1.1.0'
4+
__version__ = '1.2.0rc3'

docs/completion.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ On a Mac, install with `brew install bash-completion`
1717

1818
Place the completion script in `/etc/bash_completion.d/` (`/usr/local/etc/bash_completion.d/` on a Mac), using e.g.
1919

20-
curl -L https://raw.githubusercontent.com/docker/compose/1.1.0/contrib/completion/bash/docker-compose > /etc/bash_completion.d/docker-compose
20+
curl -L https://raw.githubusercontent.com/docker/compose/1.2.0rc3/contrib/completion/bash/docker-compose > /etc/bash_completion.d/docker-compose
2121

2222
Completion will be available upon next login.
2323

docs/install.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ First, install Docker version 1.3 or greater:
2020

2121
To install Compose, run the following commands:
2222

23-
curl -L https://github.com/docker/compose/releases/download/1.1.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
23+
curl -L https://github.com/docker/compose/releases/download/1.2.0rc3/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
2424
chmod +x /usr/local/bin/docker-compose
2525

2626
Optionally, you can also install [command completion](completion.md) for the

0 commit comments

Comments
 (0)