Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempting to start Rancher-desktop on Monterey with M1 - limatcl exited with exit code 255 #3073

Open
bconrad03064 opened this issue Oct 3, 2022 · 11 comments
Labels
kind/bug Something isn't working

Comments

@bconrad03064
Copy link

Actual Behavior

Attempting to start up rancher on new Apple M1 Pro. I'm receiving the following error when it attempts to start kube I believe. The application itself starts but when it attempts to start kubectl and load images I see the following.

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

Sometime it will throw error code 1 rather than 255.

Steps to Reproduce

Start rancher and the error pops up when attempting to start containers. I'm using a 16inch Macbook pro M1 running on Monterey.

I did try running the commands from this thread #532 but no luck.

Result

Screen Shot 2022-10-03 at 11 31 10 AM

Expected Behavior

I would expect the container to start and see it working.

Additional Information

No response

Rancher Desktop Version

1.5.1

Rancher Desktop K8s Version

1.23.3

Which container engine are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

M1

What CPU architecture are you using?

arm64 (Apple Silicon)

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

No response

Windows User Only

No response

@bconrad03064 bconrad03064 added the kind/bug Something isn't working label Oct 3, 2022
@jandubois
Copy link
Member

Looks like a duplicate of #3043.

We have some bug fixes in this area in the upcoming 1.6.0 release, hopefully later this week. Please verify if your problem is gone after upgrading.

@bconrad03064
Copy link
Author

@jandubois Great! Appreciate the quick response.

@morlay
Copy link

morlay commented Oct 26, 2022

1.6.1 still got this issue.

@morlay
Copy link

morlay commented Oct 27, 2022

it works now.

image

once I use limactl start (installed by brew install limactl)
seems lima need to initial something into ~/.lima when first run.

@AlexeyRaga
Copy link

I have installed the latest Rancher Desktop to the fresh MacBook Pro M3, Sonoma 14.2 (23C64).
Getting this error, unable to start Rancher Desktop.

I have K8s disabled, but it still complains about being not able to start k8s (same as on the screenshot above)

@young0264
Copy link

@AlexeyRaga I hava same problem.

@feitm
Copy link

feitm commented Feb 1, 2024

I have installed the latest Rancher Desktop to the fresh MacBook Pro M3, Sonoma 14.2 (23C64). Getting this error, unable to start Rancher Desktop.

I have K8s disabled, but it still complains about being not able to start k8s (same as on the screenshot above)

Same problem here.

@AlexeyRaga
Copy link

@feitm @young0264 Switch to vz engine and it'll start

@feitm
Copy link

feitm commented Feb 1, 2024

@feitm @young0264 Switch to vz engine and it'll start

Thank you, that helped.
It seems to be the solution.

@young0264
Copy link

@AlexeyRaga Thanks for your �comment.!

Using the following command, I resolved the issue.

# init
rdctl factory-reset

#change to vz
"/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/bin/rdctl" start --experimental.virtual-machine.type vz

@guysoft
Copy link

guysoft commented Sep 25, 2024

@young0264 worth noting though that it fixed the problem but also deleted all containers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants