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
p
proud-shampoo-40692
04/11/2023, 4:11 PMWhen using rancher-desktop, it uses the rancher-desktop WSL distro. Is there a way to change that...?
w
wide-mechanic-33041
04/11/2023, 4:12 PMnope that is where the cluster runs? what are you trying to do?
p
proud-shampoo-40692
04/11/2023, 4:12 PMI need a WSL with python
w
wide-mechanic-33041
04/11/2023, 4:13 PMso you can access the cluster provided by RD from other distros?
p
proud-shampoo-40692
04/11/2023, 4:13 PMthis is a single container started with docker-compose
w
wide-mechanic-33041
04/11/2023, 4:14 PMthe main distro and the data distro are meant to be “appliances” to run k3s etc
p
proud-shampoo-40692
04/11/2023, 4:14 PMNo kunernetes
w
wide-mechanic-33041
04/11/2023, 4:14 PMthats fine? its just a docker runtime
your FROM image needs to have Python in it for when you do your docker build
the rancher distro is going to run that built image, but that image can have whatever you need in it
no need to toy with the rancher distro at all