-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 3.1.0 does not work on Alpine Linux #75
Comments
Hi @bartlomiejgawel , thanks for reaching out. Thanks for the Dockerfiles, I can confirm I can reproduce the issue with v3.1 but does not happen on 3.0
Most likely yes. I managed to get this output:
I'll keep troubleshooting during the day and report back. Stay on 3.0 if possible until this is fixed 👍 |
Fixes Version 3.1.0 does not work on Alpine Linux #75
Hi @bartlomiejgawel , I have narrowed this down to |
Hello,
I've noticed a regression introduced with version 3.1.0.
You can reproduce it in the following way:
3.0.0
by running the following command:docker build -f Dockerfile -t dotnet-affected-3.0.0-alpine .
for the following
Dockerfile
file:3.1.0
by running the following command:docker build -f Dockerfile -t dotnet-affected-3.1.0-alpine .
for the following
Dockerfile
file:You can see that it works smoothly and creates an
affected.proj
file as expected.You can see that it exits with status code
139
.Notice that standard dotnet SDK works correctly (also outside the container on Windows):
3.1.0
by running the following command:docker build -f Dockerfile -t dotnet-affected-3.1.0 .
for the following
Dockerfile
file:You can see that it works smoothly and creates an
affected.proj
file as expected.I've checked what's changed between
3.0.0
and3.1.0
:v3.0.0...v3.1.0
And maybe one of the updated packages caused this regression?
The text was updated successfully, but these errors were encountered: