Skip to content
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 buildx #18

Merged
merged 1 commit into from
Feb 15, 2024
Merged

use buildx #18

merged 1 commit into from
Feb 15, 2024

Conversation

Jomik
Copy link
Contributor

@Jomik Jomik commented Feb 15, 2024

@tedivm
Copy link
Member

tedivm commented Feb 15, 2024

Buildx is the default. You don't need to set it up, you need to upgrade the build-push-action.

Check the docs: https://github.com/docker/build-push-action

GitHub Action to build and push Docker images with Buildx with full support of the features provided by Moby BuildKit builder toolkit. This includes multi-platform build, secrets, remote cache, etc. and different builder deployment/namespacing options.

Change docker/build-push-action@4976231911ebf5f32aad765192d35f942aa48cb8 to docker/build-push-action@v5 and you get it automatically.

Also caching is still a horrible idea ;-)

@AlinaNova21 AlinaNova21 merged commit d699c78 into screepers:main Feb 15, 2024
1 check passed
@Jomik
Copy link
Contributor Author

Jomik commented Feb 15, 2024

Buildx is the default. You don't need to set it up, you need to upgrade the build-push-action.

Yah, I thought so too when I set up my action, but the export failed until I added this step 🤔
Maybe outdated, unsure..?

@Jomik Jomik deleted the patch-1 branch February 15, 2024 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants