allow passthrough of Docker/Buildkit CLI options
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 41
- Avg merge
- 2h 1m
- Merged PRs (30d)
- 2
Description
With docker compose v2, there are some underlying changes to how it performs builds (mostly around the use of buildkit if available).
In order to control these, in docker compose, we can use DOCKER_BUILDKIT=0 to disable, or BUILDKIT_PROGRESS=plain to show full build debug
e.g.
BUILDKIT_PROGRESS=plain docker compose build
it would be good if we could somehow also pass these variables through Lando to aid with debugging/support. I know that you use ?dockerode to call the docker API - but no idea whether passing CLI options across is a thing
Contributor guide
No contributing guide indexed for this repository
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 tracing the Lando Docker API/dockerode path used for docker compose build, then check how Docker/BuildKit environment variables are currently handled. Define how options such as DOCKER_BUILDKIT and BUILDKIT_PROGRESS should pass through, and verify that the resulting build command supports the requested debugging behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, javascript
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100