Trouble running a pwsh command with wsl

[ssbarnea]

I am currently trying to create a symlinked directory inside the GITHUB_WORKSPACE that goes into the linux home directory, so we avoid the /mnt permission problems during our build and testing.

Still, while I was able to run the commands locally, something upsets GHA task and refuses to create the folder.

AFAIK, there is nothing wrong with mkdir -p "$wsl_home\ws", it appears to work fine locally.

The [GHA task](https://github.com/ansible/ansible-language-server/runs/7148659678?check_suite_focus=true0 looks more like:

      - shell: pwsh # <-- needed in order override the implicit wsl wrapper
        run: |
          $wsl_home=wsl --cd ~ --exec wslpath -w .;
          echo "$wsl_home";
          mkdir -p "$wsl_home\ws";
          mklink -D ws "$wsl_home\ws";
          echo "::set-output name=working-directory::$wsl_home\ws"

[Vampire]

Without having it tried, I think the problem it complains about is the $ in the path.
I would guess this is just a followup problem of "The system cannot find the file specified", which maybe means the first line did not actually execute properly?
I also do not see the output of the echo.

[Vampire]

Yep, just doing

jobs:
    foo:
        runs-on: windows-2019
        steps:
            - shell: pwsh #
              run: wsl --cd ~ --exec wslpath -w .

Already gives

The system cannot find the file specified.

And

jobs:
    foo:
        runs-on: windows-2019
        steps:
            - shell: pwsh #
              run: wsl --cd ~ --exec wslpath -w .

shows that there is no --cd option:

Usage: wsl.exe [option] ...


Options:


    -d, --distribution <DistributionName>


        Launch the specified distribition.





    -e, --exec <CommandLine>


        Execute the specified Linux command. The remainder of the arguments are


        used as the command line to execute.





    -u, --user <UserName>


        Run as the specified user.





    --help


        Display this usage information.





    --


        Stop parsing arguments and pass the remainder to the Linux process.

Even the wsl v2 wsl.exe on windows-2022 does not have the --cd option.

[ssbarnea]

LOL, The one on Windows 10 does have the --cd. Apparently it's a gamble to find wsl related commands that work on most blends and versions of Windows. You never know what works and on which version. There is no wsl --version command. They webpage does not mention anything about features being introduced in specific version of availability per Windows version.

Sorry but I will have to call it day as I need to recharge my batteries. Have a good weekend!

[Vampire]

Maybe the Kernel version from wsl --status has some meaning for that?
Maybe not, I don't know.