Not able to Connect WSL from VSCODE || WSL (21) ERROR: CreateProcessParseCommon:711: Failed to translate

[Mounesh1881]

We observed that we were running into below errors while connecting from Visual Studio to WSL.

Start: Run: wsl -l -v
[414 ms] Initializing configuration support...
[414 ms] Internal initialization of dev container support package...
[484 ms] Start: Run: wsl -d docker-desktop-data -e /bin/sh -c echo ~
[986 ms] Could not connect to WSL.
[986 ms] Command failed: wsl -d docker-desktop-data -e /bin/sh -c echo ~
[986 ms]
[986 ms] <3>WSL (21) ERROR: CreateProcessParseCommon:711: Failed to translate C:\Users\ECADMIN\AppData\Local\Programs\Microsoft VS Code
<3>WSL (21) ERROR: CreateProcessParseCommon:757: getpwuid(0) failed 2
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\Common Files\Oracle\Java\javapath
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Windows\system32
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Windows
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Windows\System32\Wbem
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Windows\System32\WindowsPowerShell\v1.0
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Windows\System32\OpenSSH
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\dotnet
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\ProgramData\chocolatey\bin
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\Amazon\AWSCLIV2
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\Docker\Docker\resources\bin
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\ProgramData\Riverbed\ProcessInjection\rpictrlBin
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\ECADMIN\AppData\Local\Microsoft\WindowsApps
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\ProgramData\Riverbed\ProcessInjection\rpictrlBin
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\ECADMIN\AppData\Local\Microsoft\WindowsApps
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\ECADMIN\AppData\Local\GitHubDesktop\bin
<3>WSL (21) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\ECADMIN\AppData\Local\Programs\Microsoft VS Code\bin
<3>WSL (21) ERROR: CreateProcessEntryCommon:334: getpwuid(0) failed 2
<3>WSL (21) ERROR: CreateProcessEntryCommon:505: execvpe /bin/sh failed 2
<3>WSL (21) ERROR: CreateProcessEntryCommon:508: Create process not expected to return

[aeschli]

docker-desktop-data is an internal distro (used by the docker implemetation).
Can you use a different distro and see if the issue exists?

[Mounesh1881]

as discussed @aeschli

please find the requested information here.

we are running .devcontainer file below the content of the file

// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/ubuntu
{
"name": "Ubuntu",
// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
"image": "mcr.microsoft.com/devcontainers/base:jammy",
"features": {
"ghcr.io/devcontainers/features/terraform:1": {}
},

// Features to add to the dev container. More info: https://containers.dev/features.
// "features": {},

// Use 'forwardPorts' to make a list of ports inside the container available locally.
// "forwardPorts": [],

// Use 'postCreateCommand' to run commands after the container is created.
// "postCreateCommand": "uname -a",

// Configure tool-specific properties.
// "customizations": {},

// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
"remoteUser": "vscode"

}

[aeschli]

This is a problem in WSL: microsoft/WSL#9252
Closing as duplicate of microsoft/WSL#9252

There are some solutions in there: Can you see if microsoft/WSL#9252 (comment) works?

[Mounesh1881]

the solution provided in #9252 is not working for me.
i want to someone can look into my issue help to resolve.

[aeschli]

@chrmarti Is it dev containers that runs wsl -d docker-desktop-data -e /bin/sh -c echo ~ ?

Maybe the current directory should not be a location on the windows file system.

[Mounesh1881]

@chrmarti Can you please help us here

[Mounesh1881]

@aeschli @chrmarti can we have update here

[aeschli]

@Mounesh1881 @chrmarti is on vacation this week, please be patient

[chrmarti]

What is the folder's path that you want to reopen in a container? Is it in a WSL or Windows filesystem?

Are any of the following settings set:

[Mounesh1881]

Just i am running this "image": "mcr.microsoft.com/devcontainers/base:jammy" only , no extra action written in code there.

[chrmarti]

Are you using a workspace folder on a Windows drive or in a WSL filesystem?

Also check the above mentioned user settings.

[Mounesh1881]

[chrmarti]

Please reply to all of the following:

1. Are you using a workspace folder on a Windows drive or in a WSL filesystem?
2. What about the Dev Containers: Execute In WSL setting? It is not part of your above screenshot.
3. What is the output of running wsl -l -v in a terminal on Windows?

[Mounesh1881]

Are you using a workspace folder on a Windows drive or in a WSL filesystem?-- not sure about this , but my code is in local drive.
What about the Dev Containers: Execute In WSL setting? It is not part of your above screenshot.

What is the output of running wsl -l -v in a terminal on Windows?

[chrmarti]

docker-desktop-data is shown as the default distro, this makes Dev Containers use this distro which is not a completely functional Linux install. Please run wsl --setdefault Ubuntu to fix this.

I also suggest you uncheck Dev Containers: Execute In WSL in the user settings unless there is a specific reason to always access the Docker CLI through WSL. (Dev Containers will still go through WSL when the workspace folder is in a WSL filesystem.)

[Mounesh1881]

thank you so much this worked for me

[chrmarti]

Thanks for confirming. Closing as answered.