This message was deleted.
# rancher-desktop
a
This message was deleted.
w
you may wnat to look at the results of
docker context ls
as it might be pointing at the wrong endpoint
g
seems normal for me
I installed docker engine manually from https://docs.docker.com/engine/install/binaries/
but now I have the following error error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/json": open //./pipe/docker_engine: Access is denied.
w
why did you need an additional dockerd? RD comes with moby?
g
dockerd is not installed with RD I am not sure why
w
it is when you select the moby container runtime
g
I selected moby container in RD but dockerd is not installed
w
do you mean docker cli in the host os? there is no install its included in their distro
do you get a hit with “where docker”
in cmd?
g
C:\Users\aabosamra>where docker C:\Program Files\Rancher Desktop\resources\resources\win32\bin\docker.exe C:\Program Files\Rancher Desktop\resources\resources\linux\bin\docker
w
cool and if you run docker info what comes up
and nothing is showing in the UI Diagnostics panel?
g
C:\Users\username>docker info Client: Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.10.4 Path: C:\Users\username\.docker\cli-plugins\docker-buildx.exe compose: Docker Compose (Docker Inc.) Version: v2.16.0 Path: C:\Users\username\.docker\cli-plugins\docker-compose.exe Server: ERROR: error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/info": open //./pipe/docker_engine: The system cannot find the file specified. errors pretty printing info
w
so bits of old docker desktop hanging around unless you installed the client tools in your host as part of your engine install
and troubleshooting in the UI looking good? Rancher icon showing blue?
The diagnostics pane saying everything a’ok?
hmmm not sure. things seem good assuming your container engine is set to dockerd
seems like kubernetes might be having some startup issues though
g
do I need to manually install dockerd on wsl ?
w
nope
click off dockerd in the prefs and any docker cli in your host should be able to interact with it after rancher restarts
g
I need to use dockerd and not nerdctl
w
yup?
so dockerd is the backend
docker is the client like nerdctl
g
I am not sure how to click off dockerd
w
most commands in nerdctl/containerd are the same so you can always alias
that was what i asked at the start?
in preferences did you select dockerd as your container engine?
g
yes
w
than it should be listening on that pipe, but seemingly it is not
g
I need to connect to dockerd using sockets from java
how to make sure that dockerd is listening on that pipe
w
did you look at the docker.log in the Log section of Troubleshooting?
g
time="2023-05-10T122033Z" level=warning msg="containerd config version
1
has been deprecated and will be removed in containerd v2.0, please switch to version
2
, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header"
I will send the log file
w
i ahve the same, but you are using dockerd runtime anyways
and a “nerdctl info” is not returning anything right (other than an error)
g
nerdctl info FATA[0000] cannot access containerd socket "/run/k3s/containerd/containerd.sock" (hint: try running with
--address /var/run/docker/containerd/containerd.sock
to connect to Docker-managed containerd): no such file or directory
w
cool so both are unresponsive
it’s listening. time=“2023-05-10T122507.151548706Z” level=info msg=“Daemon has completed initialization” time=“2023-05-10T122507.201936659Z” level=info msg=“API listen on /mnt/wsl/rancher-desktop/run/docker.sock” time=“2023-05-10T122507.213601333Z” level=info msg=“API listen on /var/run/docker.sock”
do you have a DOCKER_HOST env var that might be overriding the context?
g
echo %DOCKER_HOST% %DOCKER_HOST%
👍 1
w
has me stumped, maybe the rancher team has more ideas. only thing I could think of is security software blocking that pipe connection
may want to chime in on that issue as it sounds similar. per the log dockerd seems to be up, but docker cli can’t connect to it over the pipe for a TBD reason
you may want to try https://github.com/rancher-sandbox/rancher-desktop/issues/1580 as that shouldn’t be needed, but if it fixes your situation it may help to determine root cause
m
there are similarities for sure between the errors posted here and the two issues that are listed beforehand. per this comment (https://github.com/rancher-sandbox/rancher-desktop/issues/4412#issuecomment-1533550262), can you provide the output of various
docker
commands with dockerd/moby as the selected engine?
g
docker images error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/json": open //./pipe/docker_engine: The system cannot find the file specified. docker pull hello-world Using default tag: latest error during connect: this error may indicate that the docker daemon is not running: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/create?fromImage=hello-world&tag=latest": open //./pipe/docker_engine: The system cannot find the file specified. docker run hello-world docker: error during connect: this error may indicate that the docker daemon is not running: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/create": open //./pipe/docker_engine: The system cannot find the file specified. See 'docker run --help'. docker version Client: Version: 23.0.1-rd API version: 1.42 Go version: go1.19.5 Git commit: 393499b Built: Fri Feb 10 165632 2023 OS/Arch: windows/amd64 Context: default error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version": open //./pipe/docker_engine: The system cannot find the file specified. docker info Client: Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.10.4 Path: C:\Users\${username}\.docker\cli-plugins\docker-buildx.exe compose: Docker Compose (Docker Inc.) Version: v2.16.0 Path: C:\Users\${username}\.docker\cli-plugins\docker-compose.exe Server: ERROR: error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/info": open //./pipe/docker_engine: The system cannot find the file specified. errors pretty printing info docker ps error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: The system cannot find the file specified.
r
@gray-byte-86907, Do you still see issues with
dockerd
? If yes, Can you please try below steps? • Run the command
rdctl factory-reset
• Uninstall Rancher Desktop from
Programs & Features
• Ensure you don't have Docker Desktop running in the background • Install Rancher Desktop. You should see a first run dialog where you can select the container engine. Please select
dockerd(moby
as the container engine. • Wait till the App is up, and try running docker commands. If the issue still persists then Can you please file a bug attaching logs from your machine. You can find logs at
%USERPROFILE%//AppData/Local/rancher-desktop/logs
4074 Views