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
This has now been released in version 0.3.2! Please update and check it out.
The overall flow is that we use the RID you build for to help us pick the base image, if you use a base image that supports multiple architectures. For example, mcr.microsoft.com/dotnet/runtime:7.0 would allow you to use linux-x64, linux-arm, linux-arm64, and win-x64 to successfully target different variations of the same logical image. You can always sidestep this automatic decision by explicitly specifying your own ContainerBaseImage, for example mcr.microsoft.com/dotnet/aspnet:7.0-jammy-amd64 would specify the linux-x64 ubuntu aspnet image, with no other logic done by the tooling.
If you specify a RID that isn't compatible with the image you've chosen, we'll give an error listing out the RIDs that are compatible.
Once caveat to this is that if you'd like to use a musl-based or alpine image, you have to be aware of some caveats. I've gone into more detail in this issue.
error CONTAINER006: The Microsoft.NET.Build.Containers package does not (yet) support publishing for linux-arm6
I want to build a container running on a Kubernetes ARM cluster potentially.
Is this on the roadmap
The text was updated successfully, but these errors were encountered: