Revert "Roll back buildkit version (#758)" #768
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
This reverts commit 0af51f4.
|
Just confirmed that buildkit v0.11.2 is installed by the action: |
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
This PR reverts the changes made in #758 (commit 0af51f4).
Motivation and Context
In an update on the upstream issue docker/build-push-action#761 (comment), this has been resolved with the release of a new version of buildkit (v0.11.2), so we can roll back the mitigation we put in place to keep our docker images building.
How Has This Been Tested?
Should be good to go if CI passes and docker containers build. Would be good to check the build logs to make sure that buildkit v0.11.2 is what gets installed by CI.
Checklist