https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
w
Something different than the “Reset Kubernetes” action? Just reboot the VM w/o losing all the configs that have been made?
n
Got it. The screen 
kubernetes settings
is more about configuring the k8s version to be used, cpu, memory than resetting an existing cluster. Such actions should become part of the dashboard by the way
w
can’t speak for the Rancher team, but i think Dash was more about what was going on in the cluster and the Preferences panel is for maintaining the RD config. I believe Dash is mostly reused code from the other Rancher offerings as well so it can’t be tied to just RD.
n
So such action buttons could become part of the RD General screen then
f
I don't understand what you are asking for? Rebooting the VM is easily done by stopping and restarting Rancher Desktop? Is that what you want?
n
Why should I restart the Desktop to restart a k8s cluster ?
From my point of view, the desktop is an environment from where I should be able to configure: • VM (cpu, memory, disks, ...) • Images, Routing (= traefix), Container registry (= missing feature) • Tools (helm, ...) to be used • K8s instances
f
You can disable and re-enable k8s from inside RD. I still don't understand what you are trying to accomplish with "restarting the VM", and why restarting the app is not an obvious way to accomplish that
n
What I'm interested to do is to have the possibility using the Rancher Desktop UI to manage K8s instances (= create/delete/start/stop)
f
Oh, RD only manages a single cluster. If you want to run multiple clusters, you will need to use something like 
kind
or 
k3d
.
You can easily does this with RD and the moby runtime.
n
Good to know. Can we use the Dashboard part of RD to access a cluster created using k3d ?
f
No, it is for now intentionally limited to the cluster managed by RD itself
n
And to use k3d, a docker server must be launchd on my mac machine as otherwie I will got
Copy code
k3d cluster list
FATA[0000] runtime failed to list nodes: docker failed to get containers with labels 'map[app:k3d]': failed to list containers: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
f
That's why I said "RD and the moby runtime"
n
So RD should be also launched in this case ?
f
It does not work with plain containerd, both 
kind
and 
k3d
use the docker socket API
Yes, 
kind
and 
k3d
means "kubernetes (or k3s) in docker"
So you need to run RD as well, but you can disable kubernetes if you are not using the builtin cluster
n
Kudos 😉
6 Views
Open in Slack
PreviousNext
Powered by