Cannot start nested PWSH due to executable permission problems

[JustinGrote]

Describe the bug

Using 2-10.0

It appears there is some kind of shim used to redirect /usr/bin/pwsh to /usr/share/powershell/.store/powershell.linux.x64/7.6.1/powershell.linux.x64/7.6.1/tools/net10.0/any

It will start fine initially but if you need to start a nested powershell session, it will fail. This is because the new path gets added to PATH automatically and it tries to start from here instead of /usr/bin

Workaround

Make the "nested" pwsh executable, then it will work fine.
sudo chmod +x '/usr/share/powershell/.store/powershell.linux.x64/7.6.1/powershell.linux.x64/7.6.1/tools/net10.0/any/pwsh'

Which .NET image(s) are you using?

mcr.microsoft.com/dotnet-sdk:2-10.0

Steps to reproduce

Start bash, then start pwsh, then try to start pwsh again

Other information

No response

Output of docker version

Output of docker info

[lbussell]

Hi @JustinGrote, thanks for the report.

The image mcr.microsoft.com/dotnet-sdk:2-10.0 doesn't exist. From your screenshot it looks like you're using VS Code. Therefore I assume you are using mcr.microsoft.com/devcontainers/dotnet-sdk:2-10.0, which is based off of mcr.microsoft.com/dotnet/sdk:10.0.

The executable file you reference has these exact permissions:

-rwxr--r-- 1 root root 77K Apr 20 20:24 /usr/share/powershell/.store/powershell.linux.arm64/7.6.1/powershell.linux.$ARCH/7.6.1/tools/net10.0/any/pwsh

That file is only executable for root, and not for non-root users. That makes sense since you are running as the vscode user in your screenshot. I was able to reproduce this in the mcr.microsoft.com/dotnet/sdk:10.0 image by running su app (app is the built-in non-root user in .NET images) and then trying to run the nested pwsh session.

The exact digest I used is mcr.microsoft.com/dotnet/sdk@sha256:c0790639332692a0d56cdd81ed581cfd24d040d9839764c138994866df89a3b6.

We already set permissions to 755 on the main powershell executable here:

dotnet-docker/src/sdk/10.0/noble/amd64/Dockerfile

Line 61 in d366ed1

&& chmod 755 /usr/share/powershell/pwsh \

We can easily set permissions to 755 on the shim as well.