dotnet binary fails on Docker multiarch

[rickardp]

When running the dotnet binary under Docker multiarch (host is aarch64):

docker run --platform linux/amd64 mcr.microsoft.com/dotnet/sdk:5.0-alpine dotnet --info   
Failed to resolve full path of the current executable [/proc/self/exe]

It appears the non-Apline version has a different problem, though I did not test it very much

docker run --platform linux/amd64 mcr.microsoft.com/dotnet/sdk:5.0 dotnet --info 
Failed to create CoreCLR, HRESULT: 0x8007FF06

Possibly it could be due to the fact that the process is wrapped by the qemu-x86_64 binary.

In this case, /proc//exe points to /usr/bin/qemu-x86_64, which does not exist on the file system (i.e. not in the Docker image)

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @vitek-karas, @agocke
See info in area-owners.md if you want to be subscribed.

Issue Details

---

When running the dotnet binary under Docker multiarch, it fails with the following error message

Failed to resolve full path of the current executable [/proc/self/exe]

Possibly it could be due to the fact that the process is wrapped by the qemu-x86_64 binary.

I was not able to reproduce the problem on the official images, but it can be reproduced by downloading the Alpine binaries on a clean Alpine image.

In this case, /proc//exe points to /usr/bin/qemu-x86_64, which does not exist on the file system (i.e. not in the Docker image)

Author:	rickardp
Assignees:	-
Labels:	area-Host, untriaged
Milestone:	-

[djlawhead]

This happens to me as well, running Apple's new M1 chip. Is there a workaround?

[vitek-karas]

The docker one is probably due to the qemu layer - we would need to figure out how to determine the current process path which would work (if /proc/self/exe is not the right thing - what else).

As for Apple M1 - is it the same problem as in "running in docker using qemu emulation"?, or is it that running x64/arm64 on macOS directly is currently problematic? For the latter - we're working on it - there's a design discussion here: dotnet/designs#217

[djlawhead]

I should’ve been more specific with my reply. I receive the following

Failed to create CoreCLR, HRESULT: 0x8007FF06

When running dotnet inside of an x86_64 docker image on my Apple M1 silicon. /prof/self/exe also points to /usr/bin/qemu-x86_64 which doesn’t exist in the container. So I suspect it has more to do with docker than the M1 chip.

[deeprobin]

Both mentioned examples work on my system (host: x86-amd64-Windows).
I think we could label this arch-arm32 and arch-arm64?

[agocke]

I can't seem to repro this anymore. Closing.