Explicitly ask for the latest buildx version #1409
Merged
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.
This is a followup to complement#1399 and #1408 about things that wasn't tested as it was part of the steps to push to the official registry.
docker buildx build --push
resulted in 401 Unauthorized whiledocker push
didn't. I think the reason is that there is a bug in buildx 0.5.1 that is patched in 0.6.0 that was released an hour ago.To make it available, I explicitly declare that I want to use the latest version of buildx to make it download and install it. I noted that this made the setup take ~3 seconds longer and we can save that time by removing the explicit
latest
when this has become generally available here: https://github.com/actions/virtual-environments/blob/HEAD/images/linux/Ubuntu2004-README.md#tools