-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use Docker instead of BuildKit #506
Conversation
Signed-off-by: Ben Cressey <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🍰
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to hear from @patraw and/or @etungsten about their woes with DOCKER_BUILDKIT
to make sure there's not an edge case we're hitting.
This comment has been minimized.
This comment has been minimized.
e425f83
to
6419712
Compare
Added a fix for concurrent builds on the same host, and switched to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐳
6419712
to
1dd1528
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you please include an update to INSTALL.md
to remove BuildKit setup?
1dd1528
to
0d8965e
Compare
Done. I also filled in a |
0d8965e
to
1f48330
Compare
Backed out |
What was the reasoning there? I think I missed this conversation. |
Essentially, the desire to have changelog entries written by the same author, so the voice and focus would be consistent. |
4340a6d
to
766df7c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I don't understand all of the Docker specifics, it's clearly simpler, and fewer dependencies for our users. 🚀
Newer versions of Docker have BuildKit integrated, and we already depend on Docker to provide some of our build tools. BuildKit's ability to copy files directly out of a build image is convenient, but we can work around that using Docker functionality, and eliminate the need to run another daemon for builds. Signed-off-by: Ben Cressey <[email protected]>
Signed-off-by: Ben Cressey <[email protected]>
Although the cache volume was previously created and was functional, the subsequent build stage could not see the expected marker file under either Docker 18.09 and 19.03. With this change, the marker file is now visible, which verifies that we are using the cache volume that matches the build stage. This is a follow-up to the fix in f5c863c. Signed-off-by: Ben Cressey <[email protected]>
766df7c
to
15f4d49
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Builds for me 🔨 👍
PR #506 switches us away from needing a daemon running. Signed-off-by: Jacob Vallejo <[email protected]>
Issue #, if available:
#470
Description of changes:
Switch to the version of BuildKit integrated with Docker to simplify the build requirements.
Testing done:
Ran
cargo make clean && cargo make world
; build succeeded.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.