Support remote DOCKER_HOST by copying configs and secrets files instead of bind mounting them
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38.2k
- Forks
- 5.8k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 55
Description
Description
Per title, currently docker compose uses bind mounts to put configs and secrets in containers, but this does not work when using either docker context or DOCKER_HOST variable to remotely deploy to a different system.
This would help some of the use cases described in these issues:
- #7857
- #11141
- #5523
- #7110
- EDIT: #9648
It builds upon the config content and environment support added in https://github.com/compose-spec/compose-spec/issues/346
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 Compose config content and environment support from compose-spec issue #346, then inspect how Docker Compose currently handles config and secret bind mounts for remote deployments. Use the linked issues (#7857, #11141, #5523, #7110, and #9648) to understand expected behavior; done means configs and secrets work when using a Docker context or DOCKER_HOST pointing to another system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100