collective / collective/training-deploy-project
Docker Compose 2.0 lost --context flag
- Dominant language
- Makefile
- Stars
- 6
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
There is no --context or -c in Docker Compose 2.0. The following still works on Linux and Mac: DOCKER_CONTEXT=contextname docker-compose up -d
https://github.com/collective/training-deploy-project/blob/9b0610605f6de4fb62c944d12fc3b3b492e6dc2e/ansible/Makefile#L66
https://github.com/collective/training-deploy-project/blob/9b0610605f6de4fb62c944d12fc3b3b492e6dc2e/ansible/Makefile#L70
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with ansible/Makefile at the referenced lines 66 and 70, and inspect how Docker Compose is invoked there. Verify the commands with Docker Compose 2.0 on Linux or macOS, using the documented DOCKER_CONTEXT approach as a comparison. Done means the Makefile commands select the intended context without relying on the missing --context or -c flag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100