Error Starting Kubernetes

[gopibabus]

Actual Behavior

After opening Rancher Desktop App, It is throwing me following error

Error Starting Kubernetes

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

Some recent logfile lines:

'--tty=false',
    '/Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
  ],
  stdout: '',
  stderr: 'time="2024-03-23T14:02:19-04:00" level=info msg="Terminal is not available, proceeding without opening an editor"\n' +
    'time="2024-03-23T14:02:19-04:00" level=fatal msg="instance name \\"0\\" too long: \\"/Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/0/ssh.sock.1234567890123456\\" must be less than UNIX_PATH_MAX=104 characters, but is 104"\n',
  code: 1,
  [Symbol(child-process.command)]: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura start --tty=false /Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
}

Steps to Reproduce

1. Visit Rancher Desktop Website
2. Download Latest Version of ARM Mac Installer. At the time of my installation the version is 1.13.1
3. Install it
4. When I try to run rancher Desktop, I am getting above mentioned error

Result

Error Starting Kubernetes

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

Some recent logfile lines:

'--tty=false',
    '/Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
  ],
  stdout: '',
  stderr: 'time="2024-03-23T14:02:19-04:00" level=info msg="Terminal is not available, proceeding without opening an editor"\n' +
    'time="2024-03-23T14:02:19-04:00" level=fatal msg="instance name \\"0\\" too long: \\"/Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/0/ssh.sock.1234567890123456\\" must be less than UNIX_PATH_MAX=104 characters, but is 104"\n',
  code: 1,
  [Symbol(child-process.command)]: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura start --tty=false /Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
}

Expected Behavior

After installing Rancher Desktop on my machine (M1 Mac), it should open and show me the main window.

Additional Information

Rancher Desktop Version

1.13.1

Rancher Desktop K8s Version

1.28.4

Which container engine are you using?

containerd (nerdctl)

What operating system are you using?

macOS

Operating System / Build Version

Sonoma (14.2)

What CPU architecture are you using?

arm64 (Apple Silicon)

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

deb

Windows User Only

No response

[skalpin]

I am experiencing this today as well.

[skalpin]

Reinstalling Rancher, and setting Mount Type to reverse-sshfs, and Emulation to QEMU is working for me.

[mook-as]

Hi @gopibabus! Sorry, but it looks like your user name is a bit too long for our code. There's a workaround in https://github.com/rancher-sandbox/rancher-desktop/issues/797#issuecomment-996510877 but we still want a more automatic fix (hence that issue is still open); please try that and see if helps. If it does not, please also attach your logs so we can troubleshoot the issue.

@skalpin You probably had a different issue, as the thing you listed wouldn't have had any effect on the originally listed issue. If you encounter errors again, please feel free to open a new issue and attach your logs there instead. Thanks.

[gopibabus]

I will try and let you know @mook-as .

[skalpin]

@mook-as ty for the reply. Macos updated, and now rancher is working as expected with the VS framework and virtiofs settings. I cannot reproduce it, so I won't be making another issue.

[reslys]

I'm still experiencing the same issue on Mac Intel today, this solution worked for me https://github.com/rancher-sandbox/rancher-desktop/issues/797#issuecomment-996510877. Will leave a comment here to see if there are any updates to this issue.

[keyskey]

I got the same error but after resetting Kubernetes from GUI, it resolved.

[jandubois]

I'm closing this because the error message instance name \\"0\\" too long shows that it is a duplicate of #797.

If any commenter has a problem starting Kubernetes that does not generate this error message, then please create a separate GitHub issue to track it.