Remove Docker Buildx setup step from server CI #52
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
The Buildx builder is used by default since Moby 23.0.0, bundled into Docker Desktop 4.19
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.
The Buildx Docker backend supports building multi-arch images and is used by default since Docker Engine 23.0.0, bundled into Docker Desktop 4.19.
The default Buildx docker driver however does not support multi-arch images and so setup-buildx-action still needs to be run to set up the
docker-containerdriver. This PR is used to track whether the default driver has changed and if the Buildx setup can be avoided.See https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md for Moby/Docker version on GitHub Actions runner.