Kubernetes error when running Rancher Desktop 1.16.0 - darwin(x64)

[anjiB72]

Actual Behavior

When starting up Rancher Desktop on my Macbook Pro (MacOS Sonoma 14.7.1) I am getting this error.

Error Starting Kubernetes

Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura exited with code 1

Last command run:
/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura --debug shell --workdir=. 0 sudo update-ca-certificates

Context:
Installing CA certificates

Logfiles:
'WARNING: Skipping duplicate certificate in file ca-cert-Comodo_AAA_Services_root.pem\n' +
'WARNING: Skipping duplicate certificate in file ca-cert-Atos_TrustedRoot_Root_CA_RSA_TLS_2021.pem\n' +
'WARNING: Skipping duplicate certificate in file ca-cert-SSL.com_Root_Certification_Authority_RSA.pem\n' +
'WARNING: Skipping duplicate certificate in file'... 508 more characters,
code: 1,
[Symbol(child-process.command)]: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura --debug shell --workdir=. 0 sudo update-ca-certificates'
}
2024-11-15T08:39:10.495Z: Progress: errored Starting Backend: Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura exited with code 1

Steps to Reproduce

Open Rancher desktop on MacBook Pro, log in as admin user

Error messages as noted in Actual Behaviour shows in Pop up on screen.

Result

Please see Actual Behaviour for full details of what error I am seeing

Expected Behavior

No error pop up is shown and application starts up without any errors.

Additional Information

No response

Rancher Desktop Version

1.16.0

Rancher Desktop K8s Version

1.25.6

Which container engine are you using?

moby

What operating system are you using?

macOS

Operating System / Build Version

Sonoma 14.7.1

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

No response

[Jaizkibel]

Same error here.

Rancher-Desktop 1.6.0, MacOS 14.7.1 (M1)

Kubernetes is disabled(!)

[gunamata]

@anjiB72 , @Jaizkibel , Can you please share the application logs from your session?

[anjiB72]

@anjiB72 , @Jaizkibel , Can you please share the application logs from your session?

background.log

diagnostics.log
lima.log

@gunamata I have more but I think these hopefully should be enough

[Jaizkibel]

Hi @gunamata, here are my log files
rd_logs.zip

[BregenzerK]

I got the same problem
MacBook Pro M2, macOS 15.1.1
Rancher Desktop: 1.16.0, container engine: moby

log files:
background.log
diagnostics.log
lima.log

Has anyone found a workaround for this?

[BregenzerK]

FYI: I just got a hint from a colleague to try a factory reset and that fixed it. Might help some of you here too.

[anjiB72]

I ran a factory reset and that seems to have fixed the issue.

[DanielSincere]

I tried the factory reset, but still getting the Kubernetes error when starting up. And docker cli can't connect to the Docker daemon. This was all working fine previously on this computer.

I'm on macOS 15.2 Sequoia on an Apple Silicon chip

I also tried deleting the Rancher Desktop and rancher-desktop folders under Application Support, but still getting the error.

[jandubois]

@Jaizkibel Your issue looks the same as #6817 (certhash failing with SIGTRAP, exit 133).

#6817 was closed because it wasn't reproducible anymore after a factory reset.

One think I notice you have in common with #6817 is a cert with a name like this:

ca-cert-mkcert_development_CA_99839361094628514946333513918492060590.pem (you)
ca-cert-mkcert_development_CA_107607089142928978237251745653274906014.pem (#6817)
ca-cert-mkcert_development_CA_300552829310655388917228518891763795046.pem (#6817)

This might be a red herring (they seem to be skipped ok), but I'm curious if you know where it comes from. It looks like a local development cert is trusted as a root CA. So it might be from a man-in-the-middle proxy server, or some for your development infrastructure. But it is curious that your certs seem to follow the same naming convention.

Unfortunately I cannot detect anything else amiss in your logs.

So trying a factory reset, or upgrading to a later version of Rancher Desktop would be possible ways to resolve this issue.

[jandubois]

I ran a factory reset and that seems to have fixed the issue.

@DanielSincere without further logs it is not clear to me that you have the same issue as @anjiB72 or not. Please open a new issue and attach the logs.

Both @anjiB72 and @BregenzerK seem to have resolved their problems via factory-reset, so I'm going to close this issue.