`docker build` should print warning when args are incompatible with DOCKER_BUILDKIT configuration
Open
Nobody has claimed this yet.
area/builder
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description
docker build should print warning when args are incompatible with DOCKER_BUILDKIT configuration
Steps to reproduce the issue:
DOCKER_BUILDKIT=1 docker build --memory ...(or with any option that is incompatible with the currentDOCKER_BUILDKITconfiguration)
Describe the results you received:
No warning message was printed
Describe the results you expected:
Some warning message should be printed (ref: https://github.com/moby/moby/pull/38248)
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
The entry point is docker build, with DOCKER_BUILDKIT=1 and an incompatible option such as --memory as the reproduction. Start by tracing how the CLI handles build arguments and the BuildKit configuration; done means the command warns about incompatible arguments while preserving normal builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100