build fails with docker buildkit enabled
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 39
- Avg merge
- 18d 18h
- Merged PRs (30d)
- 1
Description
Sorry, I don't have good reproducer steps for this and I unfortunately don't have time to debug further, but when following the guide to set up galaxy-ng (https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/community/devstack/#oci-env) I found that I was unable to build until I disabled buildkit with export DOCKER_BUILDKIT=0
Possibly relevant:
https://github.com/docker/compose/issues/8538
https://github.com/docker/compose/issues/8449
I believe the issue is that buildkit tries to build in parallel but can't do that with images that depend on each other... but I haven't dug too much beyond that.
In any case exporting that env var let me work around the issue - it might be something worth considering doing in oci-env itself.
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 with the OCI environment setup guide and the oci-env entry point mentioned in the report, then reproduce the build with Docker BuildKit enabled and disabled. Compare the failure and workaround, and consider whether the environment should support BuildKit or explicitly configure DOCKER_BUILDKIT=0; done means the documented build completes without an unexplained failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100