https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
background.log
f
The diagnostics just show that you also have Docker Desktop installed, and that you are using the 
docker-buildx
and 
docker-compose
utilities from Docker Desktop. That should not be a problem.
✅ 1
It is not clear which images/containers you expect to see. If you have created / pull the images with Docker Desktop, then they will not be visible from Rancher Desktop (and vice versa) as each system is ignorant of the other and maintains their own VM and image store etc.
✅ 1
The 
background.log
file shows problems running Kubernetes because it doesn't find a the container engine. This is concerning, and the log itself doesn't include enough information; we would need to see the other log files as well to see if there are any hints into why the container engine didn't start.
c
Thank you @fast-garage-66093 I think I was confused about the docker service, Docker Desktop, and Rancher Desktop. I thought the containers and images created with Docker Desktop would be available on Rancher Desktop since those were created with docker commands on the terminal…. (My apologies, I’m pretty new to Docker things). Anyway, On Rancher, I can not see the “Add image” button in the image manager, kindly check the attachment.
f
There is something wrong with your Rancher Desktop installation; it looks like the container engine isn't starting, and the Images page is just waiting for the engine to be running.
c
~ ❯❯❯ docker ps -ls Cannot connect to the Docker daemon at unix:///Users/caro/.docker/run/docker.sock. Is the docker daemon running?
f
If you haven't tried it yet, I would recommand to first restart the application, and if that doesn't help, to do a factory reset.
If that still doesn't help, then it will be time to dive deeper into the log files.
And while I don't think this is the problem in your case, please keep in mind that you should only be running one of Docker Desktop and Rancher Desktop at a time. You should be able to switch between them, but not run them in parallel.
✅ 1
c
Ok Got it, reseting Rancher…
Yeah, I have read that, only one Desktop should be running, we can have both installed, but only one running, since both access through the same socket
Same thing, I’m not able to create a new image with Rancher. I can see in other logs I can see these errors on the k8s.log file
Copy code
2023-12-04T22:44:36.878Z: Error reading cached version data, discarding: [Error: ENOENT: no such file or directory, open '/Users/diana.tarapues/Library/Caches/rancher-desktop/k3s-versions.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/diana.tarapues/Library/Caches/rancher-desktop/k3s-versions.json'
}
2023-12-04T22:44:39.915Z: Error reading cached version data, discarding: [Error: ENOENT: no such file or directory, open '/Users/diana.tarapues/Library/Caches/rancher-desktop/k3s-versions.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/diana.tarapues/Library/Caches/rancher-desktop/k3s-versions.json'
}
diagnostics.log
In the update.log file 
2023-12-04T22:44:41.773Z: Error: Error: ENOENT: no such file or directory, open '/Users/caro/Library/Caches/rancher-desktop/updater-longhorn.json'
f
In meetings for the next few hours 😞
c
oh, got it
13 Views
Open in Slack
PreviousNext
Powered by