compose
compose copied to clipboard
docker
Define and run multi-container applications with Docker
**Description** Executing `docker-compose up` can lead to an error when a necessary image for the local platform is not available. This occurs on ARM machines, even when the platform is...
It's pretty common to have multiple .env files to override settings and is used in many projects. Some of the examples would be: - project may be configured for dev...
**Description** I would like to override service healthcheck test. Works fine on v1, but docker compose v2 do not override test value. It to append new value to previous one....
**Steps to reproduce the issue:** 1. Add the following to your docker-compose.yaml: ``` env_file: - my_env_file.env ``` 2. Add a variable containing a hyphen in its name to the .env...
--------------------------------------------------- BUG REPORT INFORMATION --------------------------------------------------- **Description** The remote socket support stopped working with compose 2.11.0. **Steps to reproduce the issue:** 1. Create an example docker-compose file 2. Try to start...
**Description** **Steps to reproduce the issue:** 1. Run `docker-compose up` 2. In another terminal run `docker-compose stop `, rename the service in docker-compose.yml and then run `docker-compose up -d `...
**Description** `docker-compose down --rmi=local` occasionally fails if an image is shared by several services. **Steps to reproduce the issue:** `docker-compose.yml`: ```yaml services: s1: build: . s2: build: . ``` `Dockerfile`:...
[Dockerfile 1.4 supports multiple build contexts](https://www.docker.com/blog/dockerfiles-now-support-multiple-build-contexts/) - a way to specify them when building in compose would be great I'd suggest something like: ```yaml services: myapp: build: contexts: additional: ../foo...
The issue in ticket (https://github.com/docker/compose/issues/6343) which was resolved in PR (https://github.com/docker/compose/pull/7762) appears to have been revived in docker-compose v2. To restate the issue, the driver_opts device parameter in volume configuration...
**What I did** Add code coverage **Related issue** **(not mandatory) A picture of a cute animal, if possible in relation with what you did**
