Detect when \.\pipe\docker_engine already exists during startup #7169
Comments
rklec
changed the title
Hmm, that's probably the issue: we fail to set up the (Windows-side) docker socket listener, so running Given your woes of installing WSL and whatnot, I guess your IT people might have done some policy things to make this not work? You might be able to get something working by switching to containerd; that might be an acceptable solution depending on what you want to do with Rancher Desktop. Either way, it would be useful to see if you can figure out why access was denied. If we can have a good way to knowing that is going to happen, we might be able to listen on a TCP port instead? (But that might take a while to implement.) |
Surprisingly, this has worked. 😆
If I would understand that thing then maybe I could help. See maybe the security products I have mentioned. |
I wonder if your experiments did set up some kind of service that already creates the named pipe instead, making it unavailable to Rancher Desktop. When Rancher Desktop is not running, could you run the following command in PowerShell: [System.IO.Directory]::GetFiles("\\.\\pipe\\") | findstr dockerIf it finds the pipe, it means there is a conflict with something else already running on your system. |
|
Well I use > [System.IO.Directory]::GetFiles("\\.\\pipe\\") | findstr docker
\\.\\pipe\\docker_engineThat said, I would argue against that this is me setting sth. up:
|
Do you have "Docker Desktop" installed on the machine? Maybe it is auto-starting or something? Anyways, I think this is a local conflict on your machine; if you manage to resolve this, the Rancher Desktop likely will start working even with |
|
Docker Desktop is not installed. But the docker service on Windows is started: And indeed, if I stop that service, it works: |
|
Ah and indeed, now also Rancher seems to work even if I switch back to dockerd., |
|
The only suggestion I would have is: could not you catch this error and show a more meaningful error message? I mean form the error itself, one would not come up with "Ah yeah, this is a conflicting docker installation!". Maybe you could hint at that potential cause, when the error happens though, so one does not need to search for GitHub or so, especially as I guess this could be a quite common error, is not it? |
Yes, I think we should detect if the named pipe already exists. I'll edit the issue subject line to reflect this.
I'm not sure about that; I don't remember seeing other GitHub issues or Slack threads about this. Normally this can only happen when people run Docker Desktop at the same time. It is quite rare that people try to setup the docker service on Windows without it. |
jandubois
changed the title
jandubois
added
kind/enhancement
jandubois
added
triage/next-candidate
Actual Behavior
I tried activating WSL support and it failed like this:
AFAIK I had Kubernetes checked and I thought let's just try... but as it did not work I have unchecked it and tried using pure Docker (which would be fine for my use case for now).
Steps to Reproduce
This could be related due to many problems:
dockerd. Unfortunately, my tries making it a real service or so always failed so far (and it was not important).I just started Rancher and let it do it's thing... activated WSL etc.
Result
see screenshot above, or in text:
This is reproducible, no matter whether I (try to) disable or (try to) enable WSL again (note the toggle in the settings is always toggled, and I can always click it again), it's always some error about
rdx-proxy.tar.Thus, I searched for
rdx-proxy.tarin the provided logs folder and found only results inbackground.log:(This is basically everything in that file... repeated several times in a similar way.)
It all looks very successful, but I cannot find useful error information. So I've just searched for "error" in all files (> 25.000 results 😆)
Warning: many logs ahead
docker.log:I also can find a lot of these errors (translated = permission denied; again repeated maybe 1000 times):
host-switch.log:k3s.log:network-setup.log(this is the whole file content):rancher-desktop-guestagent.log(again, that's the whole file):wsl-helper.log(again the permission denied errors repeated forever):docker.log:(hmm maybe I've duplicated the docker log now, messed up scrolling)
wsl.log:Edit: Oh I just noticed some errors are about
docker.exe, so these likely occur when WSL is disabled and it (apparently also with errors) tries to use the Windows docker.Expected Behavior
Installation works? Or I can at least revert my decision to use Kubernetes or somehow make this work?
Additional Information
Windows host powershell:
Inside WSL (Ubuntu 20.04.6 LTS (Focal Fossa)):
As WSL is not installed from Windows Store it's hard to get out it's version.
Rancher Desktop Version
1.14.1
Rancher Desktop K8s Version
N/A
Which container engine are you using?
dockerd
What operating system are you using?
Windows
Operating System / Build Version
Windows 10 Enterprise Version 22H2 build 19045.4529
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
None
Windows User Only
Yes some VPN, but likely unrelated as this is not a networking issue, but long before?
Rancher Desktop also installed via chocolately.
The text was updated successfully, but these errors were encountered: