You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A number of developers are now doing .NET development on Windows and Mac machines that aren't x86. I've noticed that you do offer ARM64 builds of Grate but only x86 docker images. QEMU emulation is fairly slow and doesn't appear to be officially supported by the .NET framework. It would be great to have native ARM images to get rid of emulation layer entirely from our local development process.
Describe the solution you'd like
Grate should publish linux/arm64 images
Describe alternatives you've considered
Alternatively, you could provide Alpine packages which would be sufficient as well but slightly less convenient as mentioned in #81
Additional context
The text was updated successfully, but these errors were encountered:
This one was a bit more complex than first thought, as there are no github actions runners that run on arm64 that have docker installed (the M1 agents don't have docker installed), so I'll need to migrate to using the dotnet publish to docker feature. This probably takes a bit more time, to make the image compatible
Is your feature request related to a problem? Please describe.
A number of developers are now doing .NET development on Windows and Mac machines that aren't x86. I've noticed that you do offer ARM64 builds of Grate but only x86 docker images. QEMU emulation is fairly slow and doesn't appear to be officially supported by the .NET framework. It would be great to have native ARM images to get rid of emulation layer entirely from our local development process.
Describe the solution you'd like
Grate should publish linux/arm64 images
Describe alternatives you've considered
Alternatively, you could provide Alpine packages which would be sufficient as well but slightly less convenient as mentioned in #81
Additional context
The text was updated successfully, but these errors were encountered: