Took more time on a simple step than usual
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 48
Description
There's a simple step in my Dockerfile:
RUN mv /usr/local/jdk1.8.0 /usr/local/jdk1.8.0.old
And it usually needs about 1 second:
[2024-01-23 14:12:34.121] #16 [ 3/23] RUN mv /usr/local/jdk1.8.0 /usr/local/jdk1.8.0.old
[2024-01-23 14:12:34.872] #16 DONE 0.8s
[2024-01-23 12:51:47.603] #16 [ 3/23] RUN mv /usr/local/jdk1.8.0 /usr/local/jdk1.8.0.old
[2024-01-23 12:51:48.805] #16 DONE 1.1s
But sometimes it takes much more time:
[2024-01-16 14:54:20.487] #16 [ 3/23] RUN mv /usr/local/jdk1.8.0 /usr/local/jdk1.8.0.old
[2024-01-16 14:54:37.154] #16 DONE 16.8s
The buildkitd version is v0.12.0 and the buildctl version is v0.12.1.
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 Dockerfile's RUN mv step and reproduce the timing variation using buildkitd v0.12.0 and buildctl v0.12.1. Compare the supplied build logs and investigate the BuildKit build path responsible for the step duration; done means identifying a reproducible cause or a confirmed fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100