| Commit message (Collapse) | Author | Age |
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
|
|
| |
Ignoring it on docker-compose
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
|
|
|
|
| |
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
|
|
|
|
|
|
| |
DOCKER_DEFAULT_PLATFORM env
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Shea Rozmiarek <uberpanzermensch@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add shm_size to build configuration
* Make it possible to enlarge/customize shm size during build
* Value in bytes, or use string like "512M" or "1G" ...
* Add to compose format 2.3 and (provisionally) >=3.5 format
* Add automated test for shm_size in build-opts
Signed-off-by: Marc van den Hoogen <marc@vandenhoogen.eu>
Made unit tests compatible with previously added shm_size build-option
Signed-off-by: Marc van den Hoogen <marc@vandenhoogen.eu>
Also support shm_size build-opt when conf override
Signed-off-by: Marc van den Hoogen <marc@vandenhoogen.eu>
Automated test for shm_size build-option
Signed-off-by: Marc van den Hoogen <marc@vandenhoogen.eu>
Schema 3.4, add shm_size to schema 2.3, updated const.py
Signed-off-by: Marc van den Hoogen <marc@vandenhoogen.eu>
Corrected typo in config_schema_v3.4
Signed-off-by: Marc van den Hoogen <marc@vandenhoogen.eu>
Add support for g/m/k units for shm_size in build-opts
Signed-off-by: Marc van den Hoogen <marc@vandenhoogen.eu>
Reorder imports in service.py
Signed-off-by: Marc van den Hoogen <marc@vandenhoogen.eu>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Yong Wen Chua <me@yongwen.xyz>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
|
|
| |
Remove build.labels field from 3.2 schema
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Alexey Rokhin <arokhin@mail.ru>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Daniel Nephin <dnephin@docker.com>
|
|\
| |
| | |
add IMAGE_EVENTS: load/save
|
| |
| |
| |
| | |
Signed-off-by: muicoder <muicoder@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Daniel Nephin <dnephin@docker.com>
|
|/
|
|
| |
Signed-off-by: Daniel Nephin <dnephin@docker.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Daniel Nephin <dnephin@docker.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
| |
Signed-off-by: Daniel Nephin <dnephin@docker.com>
|
|
|
|
| |
Signed-off-by: Daniel Nephin <dnephin@docker.com>
|
|
|
|
|
|
| |
Also includes several bugfixes for resolution and validation.
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
| |
Signed-off-by: Mazz Mosley <mazz@houseofmnowster.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a relative path is expanded and we're on a windows platform,
it expands to include the drive, eg C:\ , which was causing a ConfigError
as we split on ":" in parse_volume_spec and that was giving too many parts.
Use os.path.splitdrive instead of manually calculating the drive.
This should help us deal with windows drives as part of the volume
path better than us doing it manually.
Signed-off-by: Mazz Mosley <mazz@houseofmnowster.com>
|
|
|
|
| |
Signed-off-by: Daniel Nephin <dnephin@docker.com>
|
|
|
|
| |
Signed-off-by: Joffrey F <joffrey@docker.com>
|
|
|
|
|
|
|
|
|
|
|
| |
The concurrent.futures backport doesn't play well with
KeyboardInterrupt, so I'm using Thread and Queue instead.
Since thread pooling would likely be a pain to implement, I've just
removed `COMPOSE_MAX_WORKERS` for now. We'll implement it later if we
decide we need it.
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
|
|
|
|
|
| |
There's significant speed improvement by having more workers. This
value still shouldn't cause anyone's machines to melt/explode.
Signed-off-by: Mazz Mosley <mazz@houseofmnowster.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commands able to use this parallelisation are `stop`, `kill` and `rm`.
We're using a backported function from python 3, to allow us to make
the most of a pool of threads without having to write the low level
code for managing this ourselves.
A default value for number of threads is a low enough number so it
shouldn't cause performance problems but if someone knows the
capability of their system and wants to increase it, they can via
an environment variable DEFAULT_MAX_WORKERS
Signed-off-by: Mazz Mosley <mazz@houseofmnowster.com>
|
|
|
|
| |
Signed-off-by: Daniel Nephin <dnephin@gmail.com>
|
|
|
|
| |
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
|
Signed-off-by: Daniel Nephin <dnephin@gmail.com>
|