This message was deleted.
# rancher-desktop
a
This message was deleted.
i
seems to be wanting to run sudo command. That might be the issue since defualt is not allowed to run sudo
let me try applying that preference to see if fixes issue on my end
that seems to lead to another error
Copy code
'time="2024-08-27T10:13:30-05:00" level=debug msg="Failed to detect CPU features. Assuming that AES acceleration is available on this Apple silicon."\n' +
    'time="2024-08-27T10:13:30-05:00" level=debug msg="OpenSSH version 9.7.1 detected"\n' +
    'time="2024-08-27T10:13:30-05:00" level=debug msg="AES accelerator seems available, prioritizing <mailto:aes128-gcm@openssh.com|aes128-gcm@openssh.com> and <mailto:aes256-gcm@openssh.com|aes256-gcm@openssh.com>"\n' +
    `time="2024-08-27T10:13:30-05:00" level=debug msg="executing ssh (may take a long)): [/usr/bin/ssh -F /dev/null -o IdentityFile=\\"/Users/rodrigo/Library/Application Support/rancher-desktop/lima/_config/user\\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\\" -o User=rodrigo -o ControlMaster=auto -o ControlPath=\\"/Users/rodrigo/Library/Application Support/rancher-desktop/lima/0/ssh.sock\\" -o ControlPersist=yes -q -p 61858 127.0.0.1 -- cd . || exit 1 ; exec \\"$SHELL\\" --login -c 'sudo /bin/sh -c '\\"'\\"'rm -f /usr/local/share/ca-certificates/rd-*.crt'\\"'\\"'']"\n`,
  code: 255,
  [Symbol(child-process.command)]: '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura> --debug shell --workdir=. 0 sudo /bin/sh -c rm -f /usr/local/share/ca-certificates/rd-*.crt'
}
2024-08-27T15:14:46.263Z: Progress: errored Starting Backend: Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura> exited with code 255
FYI I have kubernetes disabled
p
This is similar to what I'm seeing on my tumbleweed system and another error I'm getting is failed ssh connections - disabled firewall, disabled kubernetes, factory reset, still fails at the lima initialization level.
i
I feel like might be updated related. Will see if can reset and install different version
p
My Mac instance is working without issue - and I have the same feeling on the update. I tried re-installing 1.14 but had the same issue and ran out of time last night to dig too much further, hence joining slack 😉
My latest error:
Copy code
'time="2024-08-27T09:29:49-06:00" level=info msg="[hostagent] Waiting for the essential requirement 1 of 4: \\"ssh\\""\n' +
    'time="2024-08-27T09:29:49-06:00" level=debug msg="[hostagent] executing script \\"ssh\\""\n' +
    'time="2024-08-27T09:29:49-06:00" level=debug msg="[hostagent] executing ssh for script \\"ssh\\": /bin/ssh [ssh -F /dev/null -o IdentityFile=\\"/home/user/.local/share/rancher-desktop/lima/_config/user\\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\\" -o User=user -o ControlMaster=auto -o ControlPath=\\"/home/user/.local/share/rancher-desktop/lima/0/ssh.sock\\" -o ControlPersist=yes -p 34375 127.0.0.1 -- /bin/bash]"\n' +
    'time="2024-08-27T09:31:04-06:00" level=debug msg="[hostagent] stdout=\\"\\", stde'... 5448 more characters,
  code: 1,
  [Symbol(child-process.command)]: '/opt/rancher-desktop/resources/resources/linux/lima/bin/limactl --debug start --tty=false 0'
}
2024-08-27T15:36:48.986Z: Progress: errored Starting Backend: Error: /opt/rancher-desktop/resources/resources/linux/lima/bin/limactl exited with code 1
i
yea I saw that one too on my end
nothing seem to work for me to fix things. I ended up reinstalling Version: 1.14.2 Reset rancher and things are back to working again
I had some co-workers see this issue. They mentioned . Things fixed if they updated their vm emulation
they updated from quemu to vz and it fixed it for them
I tried that and no go
ill create a git issue if no response seen here from any rancher folks
p
Interesting. I'll have to look at the version of 1.14 I installed which had the same issues. Yeah. Would love to hear from some of the rancher folks as well.
i
do you enable kubernetes on your end?
i have mine disabled since don’t use it on my end
p
I've tried with and without kubernetes and also with and without traefik enabled. Same thing. It doesn't look like it's getting past the lima vm startup but not 100% sure on that.
i
ok i tried upgrading and changed emulation to VZ + Rosetta. See things working
p
Looking at my Mac (Intel) I'm using VZ on 1.15.1 as well. Will dig into the qemu on my tumbleweed system as that seems to be the common factor.
i
yea it is not happy when you try qemu end for sure. when running 1.15.1