Open mmartin24 opened 2 years ago
Without /.rd
, the rdctl
command would need to exist elsewhere since it should be under /.rd/bin/
.
Checking if we can repro this but I'm curious with the UI and app being launchable, what steps were done. Maybe an install log would help? @prabalsharma can you check if the steps followed here are correct?
rdctl start
really isn't intended as a first-run command. As explained above, on first-run Rancher Desktop creates the ~/.rd
subtree, populates the bin
subdir, and adds code to ~/.bashrc
(or equivalent) unless told not to.
Closing this, as this is by design
I'm going to reopen this issue because I think when we have a real installer for RD, it should set things up so that rdctl start
can work for a first start.
We will need an installer on macOS to create the privileged helper application, and we'll eventually need it on Linux when we support a routable IP address and need to create a TUN device on the host.
Adding this issue to the area/installer
category.
Actual Behavior
After installing Rancher Desktop in Linux (both in Ubuntu 22.04 and in openSUSE TW) I can't initiate it using
rdctl start
; I have to userancher-desktop
instead.See attached screenshots:
Steps to Reproduce
Basically following installation steps from https://docs.rancherdesktop.io/getting-started/installation (except I am not creating
pass
Setup)[ -r /dev/kvm ] && [ -w /dev/kvm ] || echo 'insufficient privileges'
rdctl start
(it is not possible because.rd
directory is not created)Result
Expected Behavior
rdctl start
should initiate Rancher Desktop after installlAdditional Information
No response
Rancher Desktop Version
1.5.0
Rancher Desktop K8s Version
1.24.3
Which container engine are you using?
containerd (nerdctl)
What operating system are you using?
Ubuntu
Operating System / Build Version
22.04
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
deb
Windows User Only
No response