Feature request: add loadbalance driver-opt into docker-container driver
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.5k
- Forks
- 682
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 29
Description
Trying to integrate buildx in out CICD system (multi-agent)...
First design - buildx installed on every agent, registry-based shared cache used. It works as expected, but it is pretty slow on cache upload in out cases.
Alternative buildx cluster design - multiple buildx nodes with node-local cache and hash-based node selection, but loadbalance option only supported by Kubernetes driver.
But not everybody use Kubernetes, not all Kubernetes clusters support persistent storage (does buildx support StatefulSet?).
So, it would be nice to support loadbalance driver-opt in docker-container driver same way as Kubernetes driver.
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 comparing the docker-container and Kubernetes drivers, focusing on how the loadbalance driver-opt is exposed and handled. Determine the design needed to provide equivalent load balancing for docker-container without Kubernetes; done means the option works for multi-node, node-local-cache Buildx clusters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100