ENTRYPOINT w/o argument behaves differently with buildkit
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.5k
- Forks
- 682
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 29
Description
- I have tried with the latest version of Docker Desktop
- I have tried disabling enabled experimental features
- I have uploaded Diagnostics
- Diagnostics ID: 17EAB293-3DF5-4FEE-9400-A16F4036812E/20210325021752
Expected behavior
The same Dockerfile produces reasonably compatible images with and without buildkit
Actual behavior
It produces incompatible images.
Information
- macOS Version: 10.14.6
- Docker Desktop Version: 3.2.2
Steps to reproduce the behavior
run test.sh script found in https://github.com/yamt/garbage/tree/master/docker-empty-entrypoint
i put results on my environment here https://github.com/yamt/garbage/tree/master/docker-empty-entrypoint/results
i disabled buildkit following the instruction here https://docs.docker.com/docker-for-mac/release-notes/#docker-desktop-320
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
Begin with the linked garbage/docker-empty-entrypoint/test.sh reproduction and compare its recorded results with BuildKit enabled and disabled. Use the Dockerfile/ENTRYPOINT case described there as the completion check: the same Dockerfile should produce reasonably compatible images in both modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100