Docker Alpine container exit code 139

Reproduction steps

I'm running this Dockerfile with a project that uses libgit2sharp.

FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-alpine as base

EXPOSE 80

VOLUME /etc/nginx
VOLUME /etc/ssl
VOLUME /myproject

ADD tools/ssl/myproject* /etc/ssl/

# Install git.
RUN apk update && apk upgrade && \
    apk add --no-cache git openssh nano

# Build WebSite.
FROM mcr.microsoft.com/dotnet/core/sdk:3.1-alpine AS build

# Install nodejs.
RUN apk update && apk upgrade && \
    apk add --no-cache npm

# Copy everything and publish app
WORKDIR /src
COPY ./src/. .
WORKDIR /src/MyProject/WebSite
RUN dotnet publish -c release -o /app

# Final stage/image
FROM base as final

WORKDIR /app
COPY --from=build /app ./
ENTRYPOINT ["dotnet", "MyProject.WebSite.dll"]

Expected behavior

No crash.

Actual behavior

Docker container exits with code 139. There is nothing being logged from .NET. try/catch is not handling anything. There is no information in docker info. There are no logs in docker itself. I have absolutely no idea why this is crashing.

I'm using this Dockerfile for debugging in Visual Studio.

# This dockerfile is used for debugging in Visual Studio.
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-alpine

EXPOSE 80
VOLUME /etc/nginx
VOLUME /etc/ssl
VOLUME /myproject

RUN apk update && \
	apk add --no-cache nodejs npm git openssh

ADD keys/. /root/.ssh/

RUN chmod 600 /root/.ssh/*

Everything works fine here. It's running in the same container OS. The only difference is everything is built inside the container for the image, whereas debugging everything is built then copied in.

I don't know how to figure out what's going wrong at this point.

Version of LibGit2Sharp (release number or SHA1)

0.27.0.-preview-0034

Operating system(s) tested; .NET runtime tested

Docker container mcr.microsoft.com/dotnet/core/aspnet:3.1-alpine

Beginne damit, den Fehler mit dem im Issue gezeigten mehrstufigen Dockerfile und dem Visual Studio-Debugging-Dockerfile zu reproduzieren, und vergleiche deren Build- und Kopierschritte. Untersuche den Einstiegspunkt dotnet MyProject.WebSite.dll und das exit-139-Verhalten des Containers; abgeschlossen ist die Aufgabe, wenn die Ursache des nativen Absturzes identifiziert und ein bestätigter Fix oder Workaround dokumentiert wurde.