runtime: Latest 6.0 SDK/Runtime Docker images segmentation fault on ARM64
Description
When running the current mcr.microsoft.com/dotnet/sdk:6.0 image on a Raspberry Pi 3B+ with a 64-bit OS, dotnet --version segfaults.
The 7.0 images work. Older 6.0 images, like 6.0.301 also work.
Running a published application using the latest mcr.microsoft.com/dotnet/aspnet:6.0 image also segfaults. The older mcr.microsoft.com/dotnet/aspnet:6.0.8 runtime image works.
Reproduction Steps
With latest 6.0 image (SDK version 6.0.404):
# docker run -it --rm mcr.microsoft.com/dotnet/sdk:6.0
root@a9d38a1ca2dc:/# dotnet --version
Segmentation fault (core dumped)
An older image works:
# docker run -it --rm mcr.microsoft.com/dotnet/sdk:6.0.301
root@a6d6799cb152:/# dotnet --version
6.0.301
SDK 7.0 images also work:
# docker run -it --rm mcr.microsoft.com/dotnet/sdk:7.0
root@2d60270b7aeb:/# dotnet --version
7.0.101
Should be easily reproducible with an ARM64 machine at hand.
Expected behavior
The dotnet command on the current SDK 6.0 docker images shouldn’t segfault.
Actual behavior
The dotnet command on 6.0.404 segfaults.
Regression?
No response
Known Workarounds
I’m currently using the older 6.0.301 image. But that’s obviously not a permanent solution.
Configuration
No response
Other information
Please let me know, if I should test any other SDK versions or can provide some helpful output.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 25 (10 by maintainers)
dotnet-symbol looks like it is working fine now that you have a full core dump which is what I wanted to address.
Oops, I’ll check if dotnet-symbol on arm64 (and arm32 too) 6.0 core dumps.
@elinor-fung core and host_trace from my sbc too, hope it sheds some light into the issue.
host_trace.txt.gz core.17.gz