search

rancher-sandbox / rancher-desktop

Container Management and Kubernetes on the Desktop
https://rancherdesktop.io
Apache License 2.0
5.86k stars 274 forks source link

Error Starting Kubernetes, but Kubernetes is disabled #6527

Open ohare93 opened 6 months ago

ohare93 commented 6 months ago

Actual Behavior

I installed Rancher Desktop on a fresh Macbook Pro (M3) with Kubernetes disabled. Yet all I get is errors about Kubernetes not being able to start.

Steps to Reproduce

  1. Install fresh
  2. Start
  3. Failure. The Docker VM says it's started, but I cannot access it via docker commands, it says it's not running.
  4. Restart. Same issue.

Result

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

Logs


    '0'
  ],
  stdout: '',
  stderr: 'time="2024-02-26T16:41:02+01:00" level=info msg="Using the existing instance \\"0\\""\n' +
    'time="2024-02-26T16:41:02+01:00" level=info msg="Stopping vde_vmnet daemon for \\"rancher-desktop-shared\\" network"\n' +
    'time="2024-02-26T16:41:02+01:00" level=fatal msg="passwordLessSudo error: failed to run [sudo --user daemon --group everyone --non-interactive true]: exit status 1"\n',
  code: 1,
  [Symbol(child-process.command)]: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura start --tty=false 0'
}

image

Expected Behavior

Kubernetes is disabled, when I select that. It should have no impact when I simply wish to use Docker.

Additional Information

I tried to fix this myself, but with no success. Things I've tried:

  1. These steps https://github.com/rancher-sandbox/rancher-desktop/issues/6521#issuecomment-1964279780 and I get the same issue again.
  2. Turning on Kubernetes, restarting, turning it off, restarting again. No dice.

image

image

image

Rancher Desktop Version

1.12.3

Rancher Desktop K8s Version

1.28.6

Which container engine are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

MacOS Sonoma 14.3.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

jandubois commented 6 months ago

There is not enough information in these screenshots to definitely figure out what is going wrong; we would need to see all the log files.

From what I can see so far it may be that your machine doesn't allow you to configure sudo to run some privileged commands. Could you try disabling "Admin Mode" and see if that fixes things for you?

fff7d1bc commented 6 months ago

I might hit the same issue. Problem is with qemu and aarch64 boot on Apple's M3 Max. I though it was long solved, brew-installed limactl works just fine with qemu, so do UTM.

% cat lima.serial.log
UEFI firmware (version edk2-stable202302-for-qemu built at 17:14:55 on Mar 15 2023)
Error: Image at 001BFD41000 start failed: Not Found

Switching the VM to VZ from QEMU, shutting down rancher-desktop, killing remnant hung qemu process and re-starting rancher-desktop that this time boots with VZ VM is the workaround that works for me.

pfconrey commented 5 days ago

I'm having the same issue. I've attached all the relevant log fils I can find. @slashbeast's workaround did not work for me. background.log k8s.log lima.log

I'm using RD v1.15.1 on Apple Sonoma 14.5 w/M3 Pro chip

From cat lima.serial.log

UEFI firmware (version edk2-stable202302-for-qemu built at 09:21:28 on Dec 13 2023)
Error: Image at 0017FD35000 start failed: Not Found
Error: Image at 0017FC87000 start failed: Unsupported
Error: Image at 0017FC07000 start failed: Not Found
Tpm2SubmitCommand - Tcg2 - Not Found
Tpm2GetCapabilityPcrs fail!
Tpm2SubmitCommand - Tcg2 - Not Found
Image type X64 can't be loaded on AARCH64 UEFI system.
BdsDxe: failed to load Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x1,0x0)/Scsi(0x0,0x0): Not Found
BdsDxe: loading Boot0002 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xB,0x0)
BdsDxe: starting Boot0002 "UEFI Misc Device" from PciRoot(0x0)/Pci(0xB,0x0)
fff7d1bc commented 5 days ago

@pfconrey Once Rancher Desktop tries to run it and fails it will have weird state that it cannot recovery from, after you switch to VZ reboot your computer (you could try to kill the qemu processes around instead but reboot is faster). After the system boots fresh with the RD set to VZ it will work.