Skip to content

Commit a8086fa

Browse files
committed
feat(ci): multi-arch builds?
1 parent 532e89c commit a8086fa

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

.github/workflows/build_container.yaml

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,18 +44,27 @@ jobs:
4444
images: ${{ env.REGISTRY }}/${{env.IMAGE_NAME}}/${{ env.PACKAGE_NAME }}
4545
tags: |
4646
type=match,pattern=\d.\d.\d
47-
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
47+
48+
# Setup for multi-platform
49+
- name: Set up QEMU
50+
uses: docker/setup-qemu-action@v3
51+
52+
- name: Set up Docker Buildx
53+
uses: docker/setup-buildx-action@v3
54+
55+
56+
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
4857
# It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see [Usage](https://github.com/docker/build-push-action#usage) in the README of the `docker/build-push-action` repository.
4958
# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
5059
- name: Build and push Docker image
5160
id: push
52-
uses: docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4
61+
uses: docker/build-push-action@v6
5362
with:
5463
context: ${{ env.PACKAGE_NAME }}
5564
push: true
5665
tags: ${{ steps.meta.outputs.tags }}
5766
labels: ${{ steps.meta.outputs.labels }}
58-
#platforms: linux/amd64,linux/arm64
67+
platforms: linux/amd64,linux/arm64
5968

6069
# This step generates an artifact attestation for the image, which is an unforgeable statement about where and how it was built. It increases supply chain security for people who consume the image. For more information, see [AUTOTITLE](/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
6170
- name: Generate artifact attestation

0 commit comments

Comments
 (0)