Colorama is only useful on Windows by design. Since it has no effect on
other platforms, it makes sense to not require it universally.
Signed-off-by: Carl George <carl@george.computer>
This is how things were prior to the addition of the --quiet flag.
Making it not silent produces output that's weird and difficult to read.
Signed-off-by: Evan Shaw <evan@vendhq.com>
Fix for "TypeError: pull() got multiple values for keyword argument 'silent'."
This change e9b6cc23fc caused additional value to be passed for the 'silent' argument, that was already passed there: f85da99ef3
Signed-off-by: Nikita Vlaznev <nikita.dto@gmail.com>
Loading the same config file add about 100ms per each extension
service, which results in painfully slow CLI calls when a config
consists of a couple of dozens of services.
This patch makes Compose re-use config files.
Signed-off-by: Vadim Semenov <protoss.player@gmail.com>
SOCKS support will be included in the bundled (binary) version
Update some packages in requirements.txt and add some implicit deps
Signed-off-by: Joffrey F <joffrey@docker.com>
Previously docker-compose would output lines that looked like:
Starting service ... done
Starting short ...
Starting service-with-a-long-name ... done
It's difficult to scan down this output and get an idea of what's happening.
Now the statuses are aligned, and output looks like this:
Starting service ... done
Starting short ...
Starting service-with-a-long-name ... done
To me, this is quite a bit easier to read.
Signed-off-by: Evan Shaw <evan@vendhq.com>
This is how things were prior to the addition of the --quiet flag.
Making it not silent produces output that's weird and difficult to read.
Signed-off-by: Evan Shaw <evan@vendhq.com>
Fix for "TypeError: pull() got multiple values for keyword argument 'silent'."
This change e9b6cc23fc caused additional value to be passed for the 'silent' argument, that was already passed there: f85da99ef3
Signed-off-by: Nikita Vlaznev <nikita.dto@gmail.com>
- Event may contain more information in some cases.
Don't assume order or format
- Don't assume ports are always exposed on 0.0.0.0 by default
- Absence of HostConfig in a create payload sometimes causes an error at the
engine level
- In Swarm, volume names are prefixed by "<node_name>/"
- When testing against Swarm, the default network driver is overlay
- Ensure custom test networks are always attachable
- Handle Swarm network names
- Some params moved to host config in recent (1.21+) version
- Conditional test skips for Swarm environments
Signed-off-by: Joffrey F <joffrey@docker.com>
Joffrey F
Cecile Tonglet
Carl George
Harald Albers
Yong Wen Chua
Kirin Rastogi
Evan Shaw
NikitaVlaznev
Joel Barciauskas
Alexey Rokhin
Vadim Semenov
Andy Neff
dinesh
Stefan Pietsch