docker connection is case sensitive

[ritikaguptams]

Windows Version

Microsoft Windows [Version 10.0.22621.3442]

WSL Version

WSL version: 2.1.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu 20.04

Other Software

Client:
Cloud integration: v1.0.35+desktop.11
Version: 25.0.3
API version: 1.44
Go version: go1.21.6
Git commit: 4debf41
Built: Tue Feb 6 21:13:00 2024
OS/Arch: linux/amd64
Context: default

Server: Docker Desktop
Engine:
Version: 25.0.3
API version: 1.44 (minimum version 1.24)
Go version: go1.21.6
Git commit: f417435
Built: Tue Feb 6 21:14:25 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0

Repro Steps

Docker ps - with the CAPS D doesnt work whereas docker ps does:

• It works in powershell and CMD environment hence, the docker connection via WSL should also be case independent

Expected Behavior

Actual Behavior

Docker commands should run on wsl irrespective of case. As they currently do in powershell or cmd.

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[ritikaguptams]

Attaching logs: WslLogs-2024-04-03_12-43-23.zip

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Detected appx version: 2.1.5.0
Found no WSL traces in the logs

[ritikaguptams]

I guess there are no logs created for running docker via wsl, can someone from the team point me to what loags should be collected to trace docker calls via WSL ?

[zcobol]

@ritikaguptams it works as expected! When you integrate (default) WSL distro with Docker Desktop it creates the link /usr/bin/docker in your WSL instance. When you invoke the command with Docker the shell is looking for /usr/bin/Docker instead of /usr/bin/docker. Thus the failure to launch.

zcobol@TEXAS:~$ docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
zcobol@TEXAS:~$ Docker ps

The command 'Docker' could not be found in this WSL 2 distro.
We recommend to activate the WSL integration in Docker Desktop settings.

For details about using Docker Desktop with WSL 2, visit:

https://docs.docker.com/go/wsl2/

zcobol@TEXAS:~$ file /usr/bin/docker
/usr/bin/docker: symbolic link to /mnt/wsl/docker-desktop/cli-tools/usr/bin/docker
zcobol@TEXAS:~$ ls -l /usr/bin/docker
lrwxrwxrwx 1 root root 48 Apr  3 15:10 /usr/bin/docker -> /mnt/wsl/docker-desktop/cli-tools/usr/bin/docker

[benhillis]

Agreed with @zcobol - Linux is case sensitive so you must match the case of the binary you are trying to run. If you don't believe me try running BASH versus bash.

[ritikaguptams]

Thanks for explaining @zcobol ! It was weird behavior coming from Windows environment...