Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
s
stale-actor-21884
07/19/2022, 6:19 AMHello Everyone, My Mac and Fedora computers both have Rancher desktop installed and kuberenets enabled. My MacBook could ping the internal IP address of the kubectl node, but Fedora was unable to. Am I overlooking any Fedora configurations? Can someone assist me in getting ping to function on my Fedora computer?
Thank you so much for your help in advance.
I did some reading and wondered if there is any configuration that needs to be enabled in order to access the Lima VM from the host machine.
I use rancher-desktop 1.4.1 on Fedora
f
fast-garage-66093
07/20/2022, 6:13 AMThis is unfortunately not yet possible: Create a routable IP address on Linux · Issue #964 · rancher-sandbox/rancher-desktop
The only way to access the VM is via the forwarded ports