on the Mac, I have a certificate for a docker registry on some Artifactory instance, but how do I let Rancher-Deskop use it?

Auto-update to 1.8.0 has not happened today because we discovered Deployment Profile not working on my Windows 10 with the 1.8.0 release · Issue #4233 and want to fix this in a patch release. We'll continue to test the 1.8.1 tomorrow and will release later unless any more problems are detected.

Rancher Desktop 1.8.0 fails to load Kubernetes versions (the same applies to previous RD versions):

Error: No version available

wsl does not seem to have started any distribution yet up to this point:

wsl.exe --list --verbose
  NAME                    STATE           VERSION
* rancher-desktop         Stopped         2
  rancher-desktop-data    Stopped         2

The local machine has VPN and there is a company proxy. Connectivity to the Internet exists via proxy. The

checkNetworkConnectivity()

function seems to have successfully passed according to the logfile. A lookup to

<http://k3s.io|k3s.io>

seems to fail.

Hello all! I'm getting started using Rancher Desktop on a Mac with my team. My containers start properly with

docker compose up -d

from the command line, but I can find no reference to them in the Dashboard.

working on mac Apple m2 pro , Rancher Desktop version 1.8 , unable to start virtual machine , Please advise

Rancher Desktop 1.8.1 fixes the deployment profile feature on Windows. There are no other changes since 1.8.0.

Auto-update will be enabled Thursday morning if no significant problems are reported!

Hi team, I would like to allocate more cpu and memory to the VM run by rancher desktop, how can I do that? Thanks!

Good afternoon. Out of the blue this morning when trying to use rancher desktop my instance is stuck on 'error starting kubernetes' . When checking the logs, i can see this on k8s.txt :

2023-03-22T08:47:29.290Z: Updating release version cache with 130 items in cache
2023-03-22T08:47:30.943Z: Skipping pre-release v1.26.3-rc1+k3s1
2023-03-22T08:47:30.944Z: Skipping pre-release v1.25.8-rc1+k3s1
2023-03-22T08:47:30.944Z: Skipping pre-release v1.24.12-rc1+k3s1
2023-03-22T08:47:30.944Z: Found old version v1.26.2+k3s1, stopping.
2023-03-22T08:47:30.950Z: Got 130 versions.
2023-03-22T08:47:31.655Z: Ensuring images available for K3s 1.25.7
2023-03-22T08:47:34.006Z: Cache at C:\Users\nicola.a\AppData\Local\rancher-desktop\cache\k3s is valid.
2023-03-22T08:48:06.208Z: Waiting for K3s server to be ready on port 6443...
2023-03-22T08:48:06.875Z: Error: Client network socket disconnected before secure TLS connection was established
2023-03-22T08:48:07.659Z: Updating kubeconfig C:\Users\nicola.a\.kube\config...

i'm including also the k3s logs. Anyone that can help me understanding what the issue is ?

So, we're hunting down a problem where

docker pull <http://gcr.io/|gcr.io/>...

or

nerdctl pull <http://gcr.io/|gcr.io/>...

is slow when their daemon is Rancher Desktop on macOS. We've been able to isolate it to a

curl

w/ credentials from

gsutil

inside

rdctl shell

... I'm wondering if someone would be up for trying a command out for me...

Hello, I'm using rancher desktop and I wan't to ask how I can use it for local development. For now, when I use kubectl get contexts I just see my remote aks cluster. Is there any way I can find local cluster which I think should be provisioned when I have enabled kubernetes in rancher settings?

I'm enjoying Rancher Desktop so far. Something strange happened between stopping and restarting the app and VM. Now the ingress external IP is different, and it's not reachable from the host machine. I'll thread with more details.

Hi, I'm on openSUSE Tumbleweed (RD 1.7.0) and can't get the external ip to work with nginx-ingress, It's all running but when running curl I get

Failed to connect to 192.168.10.185 port 80 after 3073 ms: Couldn't connect to server

I am at this point: https://github.com/nginxinc/nginx-ingress-workshops/blob/main/Rancher/labs/lab3/readme.md#verify-access-to-the-ingres[…]roller-using-the-external-ip

@curved-army-69172 has left the channel

Hi All, I'm using Rancher Desktop on Mac as Docker Desktop replacement. Now I need to pull images from our internal registry with a self signed certificate. How can I tell rancher Desktop to ignore the certificate error? I'm using rancher with containerd. Using dockerd would also be fine for my usecase.

Hi, I am using Rancher Desktop and i created 2 kubernetes pods but i am facing problem to do pod to pod communication RD version: 1.7.0

MacBook Pro (16-inch, 2019), MacOS 10.15.7, 2.6 GHz 6-Core Intel Core i7, 16 GB 2667 MHz DDR4 Rancher 1.7.0 After running a pretty intensive docker image (not kubernetes) I have a considerable amount of CPU usage. No containers are running. kernel_task appears to be the problem. What might I have broken?

Oh, and I quit Rancher Desktop as well, so it is not running.

After I installed VMware Fusion on my Intel Mac (Ventura), Rancher Desktop does not start anymore. The part of the log is:

'time="2023-03-23T09:40:52-07:00" level=fatal msg="errors inspecting instance: [failed to get Info from \\"/Users/oleg/Library/Application Support/rancher-desktop/lima/0/ha.sock\\": Get \\"<http://lima-hostagent/v1/info>\\": dial unix /Users/oleg/Library/Application Support/rancher-desktop/lima/0/ha.sock: connect: connection refused]"\n',
  code: 1,
  command: [
    '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl>',
    'start',
    '--tty=false',
    '0'
  ]
}

Anyone knows what’s going on and how to fix it? @fast-garage-66093?

Does anyone already installed NeuVector in Rancher Desktop? I tried to install using the manifests and helm. For both methods the enforcer pod keeps crashing.

pod/neuvector-enforcer-pod-4qjdl               0/1     CrashLoopBackOff

This is the enforcer pod logs and this is the moment that the pod fails.

2023-03-23T20:48:43.574|INFO|AGT|main.waitForAdmission: Node admission is enabled
2023-03-23T20:48:43.574|INFO|AGT|main.waitForAdmission: Sending join request
2023-03-23T20:48:43.575|INFO|AGT|cluster.newGRPCClientTCP: Expected server name - cn=NeuVector
2023-03-23T20:48:43.578|INFO|AGT|main.waitForAdmission: Agent join request accepted
2023-03-23T20:48:43.581|INFO|AGT|main.main: Runtime storage driver - name=overlayfs
2023-03-23T20:48:43.581|INFO|AGT|dp.Open:
2023-03-23T20:48:43.596|INFO|AGT|probe.New:
2023-03-23T20:48:43.596|ERRO|AGT|probe.NewFileAccessCtrl: FA: Initialize - error=function not implemented
2023-03-23T20:48:43.596|INFO|AGT|probe.New: PROC: Process control is not supported
2023-03-23T20:48:43.605|INFO|AGT|main.(*Bench).RerunKube:
2023-03-23T20:48:43.608|ERRO|AGT|system.(*SystemTools).CheckHostProgram: Done - error=exit status 255 msg=Failed to run script: ret=1

2023-03-23T20:48:43.608|ERRO|AGT|main.(*Bench).checkRequiredHostProgs: - error=exit status 255 program=kubectl
2023-03-23T20:48:43.609|ERRO|AGT|main.(*Bench).RerunKube: Cannot run master node CIS benchmark - error=kubectl command not found.

2023-03-23T20:48:43.614|INFO|AGT|main.(*Bench).RerunKube: Not a kubernetes worker node
2023-03-23T20:48:43.618|ERRO|AGT|fsmon.NewFileWatcher: Open fanotify fail - error=function not implemented
2023-03-23T20:48:43.618|INFO|AGT|probe.(*Probe).netlinkProcMonitor: PROC: Start real-time process listener
2023-03-23T20:48:43.618|ERRO|AGT|main.main: Failed to open file monitor! - error=function not implemented
2023-03-23T20:48:43|MON|Process agent exit status 254, pid=9363
2023-03-23T20:48:43|MON|Process agent exit with non-recoverable return code. Monitor Exit!!
2023-03-23T20:48:43|MON|Kill dp with signal 15, pid=9362
Leave the cluster
2023-03-23T20:48:43|DEBU|dp0|dp_data_thr: dp thread exits
2023-03-23T20:48:43.651Z [INFO]  agent.client: client starting leave
2023-03-23T20:48:44.237Z [INFO]  agent.client.serf.lan: serf: EventMemberLeave: 10.42.0.10 10.42.0.10
2023-03-23T20:48:47.817Z [INFO]  agent: Requesting shutdown
2023-03-23T20:48:47.817Z [INFO]  agent.client: shutting down client
2023-03-23T20:48:47.840Z [INFO]  agent: consul client down
2023-03-23T20:48:47.840Z [INFO]  agent: shutdown complete
2023-03-23T20:48:47.840Z [INFO]  agent: Stopping server: address=127.0.0.1:8500 network=tcp protocol=http
Graceful leave complete
2023-03-23T20:48:47.841Z [INFO]  agent: Waiting for endpoints to shut down
2023-03-23T20:48:47.841Z [INFO]  agent: Endpoints down
2023-03-23T20:48:47.841Z [INFO]  agent: Exit code: code=0
2023-03-23T20:48:47|MON|Clean up.

This is the describe output

Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  11m                   default-scheduler  Successfully assigned neuvector/neuvector-enforcer-pod-4qjdl to lima-rancher-desktop
  Normal   Pulling    11m                   kubelet            Pulling image "<http://docker.io/neuvector/enforcer:5.0.4|docker.io/neuvector/enforcer:5.0.4>"
  Normal   Pulled     10m                   kubelet            Successfully pulled image "<http://docker.io/neuvector/enforcer:5.0.4|docker.io/neuvector/enforcer:5.0.4>" in 22.298088477s (22.298104263s including waiting)
  Normal   Created    7m50s (x5 over 10m)   kubelet            Created container neuvector-enforcer-pod
  Normal   Started    7m50s (x5 over 10m)   kubelet            Started container neuvector-enforcer-pod
  Normal   Pulled     6m4s (x5 over 10m)    kubelet            Container image "<http://docker.io/neuvector/enforcer:5.0.4|docker.io/neuvector/enforcer:5.0.4>" already present on machine
  Warning  BackOff    68s (x34 over 9m45s)  kubelet            Back-off restarting failed container

Any idea why is this happening?

After starting the rancher, when I am trying to build the image, getting following error: ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

How can we set the

mountType: 9p

in Windows ?

Hey folks, I’m attempting to use tilt with Rancher Desktop and I’m running into an issue where tilt isn’t identifying a “Cluster Local Registry” … I’m wondering what direction to go in to attempt to solve that.

Rancher Desktop automatic update to 1.8.1 made my malware scanner fire all alarm bells. 2 of the VirusTotal scanners found the same malware: Gen:Variant.Tedy Can someone verify?

@calm-sugar-3169 I just saw that my issue about proxy (https://github.com/rancher-sandbox/rancher-desktop/issues/4013) got added to the 1.9 milestone. I had the occasion to test my changes with the

experimental.rdNetworking

features and it seems to be working as expected. Did you had the occasion to test the feature yourself with a proxy ? Is there anything I can do to help you with the integration for the next version ? I can do a proper pull request to discuss the code.

What do most folks do when utilizing containerd as the container engine for the cluster local registry?

@proud-jewelry-46860: i'd like to change the /getting-started/installation page's head.... it'd be nice if the first thing was links to the various platforms (macOS, Windows, Linux)... The sidebar is really too far away and too spread out...

My Windows 11 Rancher Desktop didn't work... Am I wrong in expecting that if I use the installer, it should "just work™"?