Roll back buildkit version #758
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Well this build worked. Not really proof this fixes the issue, since its intermittent anyway, but seems like this workaround couldn't hurt? |
|
Added additional debug option suggested, so if it fails we get some logs that might be useful to send upstream to troubleshoot. |
jonathangreen
added a commit
that referenced
this pull request
Jan 27, 2023
This reverts commit 0af51f4.
2 tasks
jonathangreen
added a commit
that referenced
this pull request
Jan 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
It seems like our docker builds have been failing a lot recently with the message:
Motivation and Context
It looks like there are two upstream issues where others are seeing this:
docker/build-push-action#761
moby/buildkit#3347
One suggestion was to roll back the version of buildkit we are using temporarily. It appears this issue is correlated with the release of buildkit v11, so this may fix the issue.
Once there is a fix for this in buildkit, we will have to revert this fix so we are getting the latest version again.
How Has This Been Tested?
Going to let CI run and see if it works.