alpine3.16 runtime prints stack trace but alpine3.17 doesn't

[andysbolton]

Hi, I can't tell if this is related to a bug or my own misconfiguration, but I would love another opinion.

I've noticed that changing my dotnet runtime from mcr.microsoft.com/dotnet/aspnet:6.0.13-alpine3.16 to mcr.microsoft.com/dotnet/aspnet:6.0.13-alpine3.17 results in a stack trace no longer printing to standard out when I run a container with a non-zero exit code. Please see this repo for an example.

Given a simple program targeting mcr.microsoft.com/dotnet/aspnet:6.0.13-alpine3.16 that throws an exception, a stack trace is printed:

But it will not be printed when targeting mcr.microsoft.com/dotnet/aspnet:6.0.13-alpine3.17:

Furthermore, if I exec into a container with the mcr.microsoft.com/dotnet/aspnet:6.0.13-alpine3.17 runtime and run dotnet alpine317segfault.dll, I receive a segmentation fault:

docker -v                                                                                                         
Docker version 20.10.22, build 3a2c30b

Is this something I should take up with alpine? Is there something else obvious that I'm missing?

Thanks!

[mthalman]

It looks like you're running into this: dotnet/runtime#81218