Skip to content

Conversation

WyriHaximus
Copy link
Member

No description provided.

@bendavies
Copy link

qemu can be removed now can't it?

@WyriHaximus
Copy link
Member Author

qemu can be removed now can't it?

Depends, if the platform matches the runner arch yes. Otherwise no. But I also want to turn this into a reusable work flow, and since I build the same platforms as the upstream image it needs to be dynamic. And I'm also working on building in qemu on my own runner images so I should do an check if it's already there or not

@WyriHaximus
Copy link
Member Author

@bendavies Also I want to merge #20 before finishing this one

@WyriHaximus WyriHaximus force-pushed the Run-ARM-image-build-+-CVE-Scan-+-Test-on-ARM-machines branch 3 times, most recently from 55e527d to d8a2df2 Compare March 8, 2025 20:46
images: ${{ env.REGISTRY_IMAGE }}
- name: Set up QEMU
uses: docker/setup-qemu-action@v3
if: ${{ !contains(matrix.platform, 'arm') && !contains(matrix.platform, 'amd64') }}
Copy link
Member Author

@WyriHaximus WyriHaximus Mar 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bendavies As you suggested, not installing QEMU during runs when the image we're building is for arm64 or amd64. But still installing it for others, which will be never in for this image, unless the upstream image starts supporting more platforms

@WyriHaximus WyriHaximus force-pushed the Run-ARM-image-build-+-CVE-Scan-+-Test-on-ARM-machines branch from d8a2df2 to 733c8db Compare March 8, 2025 21:23
@WyriHaximus WyriHaximus merged commit 33bc83d into main Mar 9, 2025
9 checks passed
@WyriHaximus WyriHaximus deleted the Run-ARM-image-build-+-CVE-Scan-+-Test-on-ARM-machines branch March 9, 2025 08:57
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.

2 participants