https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
c
i tried to edit lima.yaml and change the socket option, but on restart it just added a new set of sockets with the /var/run/docker.socket back...
Copy code
portForwards:
  - guestPortRange:
      - 1
      - 65535
    guestIPMustBeZero: true
    hostIP: 0.0.0.0
  - guestSocket: /var/run/docker.sock
    hostSocket: /home/gabriel/.rd/docker.sock
  - guestSocket: /var/run/rancher.sock
    hostSocket: /home/gabriel/.rd/rancher.sock
i see that using the "sudo" option and selecting MOBY does create a context. didn't get that with containerd...
Copy code
rancher-desktop *   Rancher Desktop moby context              unix:///home/gabriel/.rd/docker.sock   <https://127.0.0.1:6443> (default)
p
Hmm, Rancher Desktop should (ask you about it before asking for your password, with a checkbox to say never ask for the password (and run without sudo). Which version are you using?
c
latest as of now (1.4.1). i do see the checkbox. but i have no idea what will happen if I check that box
after a few factory resets and different settings, i did get the context only if using moby.
p
Sounds like we need to phrase that better. I'm on mac, but it should be the same:
c
on linux, i got a different message. didn't mention context
p
Yeah, currently with nerdctl we actually run the command inside our VM (because it needs access to disks and things internally, so we can't just expose a socket the way we do with docker)
👍 1
c
[the description on your image] was what i wanted :) i will keep the working setup for now. but as soon as i have some time i will try moby+non-sudo
thanks for the help on this. for future reference, if i try to do the setup i wanted, anyone know where it is documented the manual socket/context setup? do i have to create the context too?
p
No, the context is created for you; the hope was that the big paragraph in the screenshot was enough. But obviously it's a bit lacking 😄
Took way too long to get this, but this is the corresponding Linux screen shot:
(I realize it looks exactly the same)
f
You should only ever get the dialog on Linux when using docker. I don't think there is any need to use sudo with containerd/nerdctl at all. (It does run as 
root
, but only inside the VM, so doesn't need 
root
on the host)
c
did get the dialog again, using nerdctl (enabled 
always run without admin access
this time). i guess since now i have the context showing up, things work fine regardless.
f
The context is only used by moby/docker, so I don't understand why you would get the dialog
c
hum.. i did mess around with my yaml files a lot but i did try to clean them all and factory reset to the best of my abilities. i got it when i turned the computer on and started docker-desktop again. never run anything as sudo (besides that one time i did gave it my password for the admin feature) i restarted it a few times now. seems my UI is weird. i always get the dialog, even after checking the "always run..." only thing that prevented the dialog on startups was to unselect "Allow sudo access" on the "Application settings" tab
271 Views
Open in Slack
PreviousNext
Powered by