Adopt compose-specification for compose file support in `docker stack` command
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
https://compose-spec.io/ is now the place to define Compose file format and evolution. Changes like https://github.com/docker/cli/pull/2517 should not happen within this repo anymore without a sibling issue/PR on compose-spec.
http://github.com/compose-spec/compose-go was contributed as a git extraction for the types and loader packages from docker/cli. To avoid code to diverge, docker/cli should adopt compose-go ASAP
last but not least, using compose-go would make docker stack command compliant with the compose specification, and allow to mix docker compose config command with docker stack deploy (which seem to be a common pattern)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the docker/cli code behind the docker stack command and its existing Compose types and loader packages. Compare that implementation with compose-go and the compose-spec, then verify that docker compose config output can be used with docker stack deploy without divergence from the specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100