Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
e
elegant-memory-40145
07/13/2022, 9:32 PMIs there any way to install Rancher Desktop without an internet connection? If not is there a feature request to allow users to do this? Thanks!
k
kind-iron-72902
07/13/2022, 11:48 PMHi, we are working on this right now, targeting the next release. Please let me know if you can't wait and I'll post the instructions.
e
elegant-memory-40145
07/14/2022, 12:47 AMThank you! I would appreciate the instructions, I'm running on Windows 10.
f
fast-garage-66093
07/14/2022, 12:54 AMI'll let @kind-iron-72902 post the instructions, but for now we are targeting offline-operation, not offline installation. The latter would be do-it-yourself by copying the installation and cached image to the offline machine yourself.
Relevant issues that you may want to follow are Epic: Make sure Rancher Desktop works properly without a network connection · Issue #2130 · rancher-sandbox/rancher-desktop and Offline installation for Rancher Desktop · Issue #888 · rancher-sandbox/rancher-desktop
k
kind-iron-72902
07/14/2022, 1:27 AMUnfortunately Version 1.5.0 1.4.1 will still fail to start up in an offline environment when it tries to hit the channel server looking to see if there are new versions of kubernetes.
I just realized that now. Sorry about that -- I'll get everyone to work harder to make sure we get this next release out 🙂
e
elegant-memory-40145
07/14/2022, 1:28 AMohh snap, do you have an ETA on the next release? Also can I revert to an earlier version to get offline working?
f
fast-garage-66093
07/14/2022, 1:28 AMYou mean 1.4.1, right? 1.5.0 is the upcoming release, which should have these fixes.
k
kind-iron-72902
07/14/2022, 1:28 AMSorry, right...
I don't know if offline ever worked.
f
fast-garage-66093
07/14/2022, 1:29 AMETA will be the end of the month, or early August, but it is just an ETA, not a promise/commitment :)
k
kind-iron-72902
07/14/2022, 1:30 AMAnd is it installation that's failing, or running after installed? I've been focused on initializing it when connected, shutting down, and then continuing to run after disconnecting. Installing will be a different story
e
elegant-memory-40145
07/14/2022, 1:31 AMactually both for us, we will need to be able to install and initialize in an offline environment.
f
fast-garage-66093
07/14/2022, 1:31 AMOffline installation is out of scope for 1.5.0, except that copying an working setup including caches to an offline machine is supposed to work, and shall be documented
k
kind-iron-72902
07/14/2022, 1:31 AMI haven't looked at the issues for offline installation yet
f
fast-garage-66093
07/14/2022, 1:32 AMFor starters, the RD installer does not include the airgap images, or specific kubectl versions, so you have to get them from "somewhere".
e
elegant-memory-40145
07/14/2022, 1:33 AMok, that would provide an acceptable workaround for us if we could copy in the cached files from an online installation.
f
fast-garage-66093
07/14/2022, 1:33 AM@elegant-memory-40145 Are you interested in running kubernetes or just containerd/dockerd? The latter may be easier
k
kind-iron-72902
07/14/2022, 1:33 AMFrom my investigation so far, it's enough to copy the files from
$HOME/AppData/Local/rancher-desktop/cache$HOME/.kuberlre
elegant-memory-40145
07/14/2022, 1:34 AMwe are interested in running kubernetes, we have a microservice application
k
kind-iron-72902
07/14/2022, 1:34 AMBut like I said, right now Rancher Desktop 1.4.1 will fail to start up if it can't connect to the github kubernetes channel server
f
fast-garage-66093
07/14/2022, 1:35 AMGuna claimed that it worked for him, but I don't see how. Anyways, I think waiting for 1.5.0 is the way to go
e
elegant-memory-40145
07/14/2022, 1:36 AMok, I appreciate the information, we really like Rancher Desktop for the local K8s installation, we're trying to get away from our previous Docker Desktop version of our software
f
fast-garage-66093
07/14/2022, 1:37 AMThere should be a writeup in the docs on how to do this with 1.5.0. Maybe it will come a little after the release date, depending on how busy docs are, but it should be documented and supported.
Ask back here if it doesn't work for you, or raise a Github issue (preferable, because messages here quickly get lost)
e
elegant-memory-40145
07/14/2022, 1:38 AMok, I can give it a shot on the 1.4.1 and report back
f
fast-garage-66093
07/14/2022, 1:39 AMThe first thing to try is once you have a working setup, to completely disconnect from the network and see if you can still start it up and use it. We now have conflicting reports if this is possible with 1.4.1 or not.
If this works, then it should be possible to transfer the setup to another offline machine.
If we are talking about Windows here, then I assume the offline machines are already setup with the latest WSL2 and kernel configured
e
elegant-memory-40145
07/14/2022, 1:41 AMyep
ok, so I do get errors trying to start rancher desktop, once I kill my network connection but I think this is because the .kube config file is pointing to an ip address for the cluster. This probably needs to change to localhost?
f
fast-garage-66093
07/14/2022, 1:49 AMThat is possible. We actually ship kuberlr/Makefile at master · flavio/kuberlr, which will check the kube version of the server and then download the corresponding client version.
So if the current context cluster is not reachable, you may get weird error messages from kubectl