This message was deleted.
# rancher-desktop
a
This message was deleted.
f
No, this is not configurable. I don't expect it to take much time at all though.
n
shrug, I'm on a M3 max mbp and it's taking several minutes per-cycle, even after doing the "factory reset" option since I'm trying to get a clean state to open an issue
f
Not sure what you mean by "it" exactly. Shutting down Rancher Desktop?
n
Correct. I'm trying to start and re-start rancher desktop to try and figure out what's triggering a bug which causes port-forwarding to not work
f
That sounds wrong, Shutting down Rancher Desktop should take maybe 10 seconds, and a factory-reset is basically instantaneous. There must be something else wrong.
n
It seems very slow, but this is the last line in the log, which will hang for quite a while:
Copy code
time="2026-05-18T17:46:09-05:00" level=debug msg="executing ssh (may take a long)): [/usr/bin/ssh -F /dev/null -o IdentityFile=\"/Users/meloam/Library/Application Support/rancher-desktop/lima/_config/user\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o GSSAPIAuthentication=no -o Ciphers=\"^aes128-gcm@openssh.com,aes256-gcm@openssh.com\" -o User=meloam -o ControlMaster=auto -o ControlPath=\"/Users/meloam/Library/Application Support/rancher-desktop/lima/0/ssh.sock\" -o ControlPersist=yes -o LogLevel=ERROR -p 64969 127.0.0.1 -- cd . || exit 1 ; exec \"$SHELL\" --login -c 'sudo /sbin/fstrim /mnt/data']"
.... I'll let it sit for a while to report the subsequent logs
nope it's just the networking issue, I misdiagnosed 😞
Copy code
2026-05-18T22:49:19.472Z: > limactl --debug stop 0
$ l [Error]: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1
    at ChildProcess.<anonymous> (file:///Applications/Rancher%20Desktop.app/Contents/Resources/app.asar/dist/app/background.js:2:68266)
    at ChildProcess.emit (node:events:519:28)
    at ChildProcess._handle.onexit (node:internal/child_process:293:12) {
  command: [
    '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl>',
    '--debug',
    'stop',
    '0'
  ],
  stdout: '',
  stderr: 'time="2026-05-18T17:46:09-05:00" level=debug msg="ResolveVMType: resolved VMType \\"vz\\" (explicitly specified in []*LimaYAML{o,y,d}[1])"\n' +
    'time="2026-05-18T17:46:09-05:00" level=debug msg="Failed to look up socket_vmnet path \\"/opt/socket_vmnet/bin/socket_vmnet\\"" error="exec: \\"/opt/socket_vmnet/bin/socket_vmnet\\": stat /opt/socket_vmnet/bin/socket_vmnet: no such file or directory"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="Sending SIGINT to hostagent process 56247"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="Waiting for the host agent and the driver processes to shut down"\n' +
    'time="2026-05-18T17:46:09-05:00" level=debug msg="received an event" event="{2026-05-18 16:40:20.442637 -0500 CDT {false false false [] 64969}}"\n' +
    'time="2026-05-18T17:46:09-05:00" level=debug msg="received an event" event="{2026-05-18 16:40:40.689253 -0500 CDT {true false false [] 64969}}"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="[hostagent] 2026/05/18 16:40:24 tcpproxy: for incoming conn 127.0.0.1:65223, error dialing \\"192.168.5.15:22\\": connect tcp 192.168.5.15:22: no route to host"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="[hostagent] 2026/05/18 16:40:24 tcpproxy: for incoming conn 127.0.0.1:65222, error dialing \\"192.168.5.15:22\\": connect tcp 192.168.5.15:22: no route to host"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="[hostagent] 2026/05/18 16:40:28 tcpproxy: for incoming conn 127.0.0.1:65225, error dialing \\"192.168.5.15:22\\": connect tcp 192.168.5.15:22: no route to host"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="[hostagent] 2026/05/18 16:40:28 tcpproxy: for incoming conn 127.0.0.1:65224, error dialing \\"192.168.5.15:22\\": connect tcp 192.168.5.15:22: no route to host"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="[hostagent] 2026/05/18 16:40:29 tcpproxy: for incoming conn 127.0.0.1:65226, error dialing \\"192.168.5.15:22\\": connect tcp 192.168.5.15:22: connection was refused"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="[hostagent] 2026/05/18 16:40:30 tcpproxy: for incoming conn 127.0.0.1:65227, error dialing \\"192.168.5.15:22\\": connect tcp 192.168.5.15:22: connection was refused"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="[hostagent] 2026/05/18 16:40:31 tcpproxy: for incoming conn 127.0.0.1:65228, error dialing \\"192.168.5.15:22\\": connect tcp 192.168.5.15:22: connection was refused"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="[hostagent] 2026/05/18 16:40:33 tcpproxy: for incoming conn 127.0.0.1:65229, error dialing \\"192.168.5.15:22\\": connect tcp 192.168.5.15:22: connection was refused"\n' +
    'time="2026-05-18T17:46:09-05:00" level=info msg="[hostagent] 2026/05/18 16:40:35 tcpproxy: for incoming conn 127.0.0.1:65230, error dialing \\"192.168.5.15:22\\": connect tcp 192.168.5.15:22: connection was refused"\n' +
    'time="2026-05-18T17:49:19-05:00" level=fatal msg="did not receive an event with the \\"exiting\\" status"\n',
  code: 1,
  signal: undefined,
  [Symbol(child-process.command)]: '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> --debug stop 0'
}
f
This is how quitting Rancher Desktop looks for me;
fstrim
takes 5 seconds:
Copy code
2026-05-18T22:47:02.635Z: > /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> shell --workdir=. 0 sudo /sbin/rc-service --ifstarted containerd stop
2026-05-18T22:47:02.679Z: > /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> shell --workdir=. 0 sudo /sbin/rc-service --ifstarted rd-openresty stop
2026-05-18T22:47:02.731Z: > /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> shell --workdir=. 0 sudo /sbin/fstrim /mnt/data
2026-05-18T22:47:07.345Z: > limactl stop 0
time="2026-05-18T15:47:02-07:00" level=info msg="Sending SIGINT to hostagent process 93366"
time="2026-05-18T15:47:02-07:00" level=info msg="Waiting for the host agent and the driver processes to shut down"
time="2026-05-18T15:47:02-07:00" level=info msg="[hostagent] 2026/05/18 15:46:06 tcpproxy: for incoming conn 127.0.0.1:57791, error dialing \"192.168.5.15:22\": connect tcp 192.168.5.15:22: connection was refused"
time="2026-05-18T15:47:02-07:00" level=info msg="[hostagent] 2026/05/18 15:46:23 tcpproxy: for incoming conn 127.0.0.1:57798, error dialing \"192.168.5.15:22\": connect tcp 192.168.5.15:22: connection was refused"
time="2026-05-18T15:47:02-07:00" level=info msg="[hostagent] Received SIGINT, shutting down the host agent"
time="2026-05-18T15:47:02-07:00" level=info msg="[hostagent] Shutting down the host agent"
time="2026-05-18T15:47:02-07:00" level=info msg="[hostagent] Stopping forwarding \"/var/run/docker.sock\" (guest) to \"/Users/jan/.rd/docker.sock\" (host)"
time="2026-05-18T15:47:02-07:00" level=info msg="[hostagent] Shutting down VZ"
time="2026-05-18T15:47:04-07:00" level=error msg="[hostagent] dhcp: unhandled message type: RELEASE"
time="2026-05-18T15:47:06-07:00" level=info msg="[hostagent] [VZ] - vm state change: stopped"
time="2026-05-18T15:47:06-07:00" level=error msg="[hostagent] accept tcp 127.0.0.1:57783: use of closed network connection"
time="2026-05-18T15:47:06-07:00" level=info msg="Waiting for the instance to shut down"
time="2026-05-18T15:47:07-07:00" level=info msg="The instance 0 has shut down"
n
I see you're one of the devs from looking at GH, I suspect that what actually happened is I somehow got macos into a state where the "Local Network" permissions on seqoia got screwed up. I"m digging up my old MBP to install RD and compare the two
f
Are you running with "admin mode" enabled? Because this seems to be your real issue:
Copy code
Failed to look up socket_vmnet path \\"/opt/socket_vmnet/bin/socket_vmnet\\"" error="exec: \\"/opt/socket_vmnet/bin/socket_vmnet\\": stat /opt/socket_vmnet/bin/socket_vmnet: no such file or directory"\n'
But
socket_vmnet
is only used when admin mode is enabled
n
I am
But I"m also not getting prompted via sudo
f
Do you actually need it though?
n
What got me down this path is that I couldn't access a container from the host (e.g.
nerdctl run -p 8080:8008
). I've tried both with and without the admin mode with no success
If I do lsof from the host, the port isn't bound (but I don't know enough about how the networking is setup to know whether or not guest ports would show up that way on the host)
f
The socket location looks wrong, but if the sudo prompt never showed, then not sure how this got configured. I would recommend disabling admin mode. It only provides 2 things:
/var/run/docker.sock
in the default location, and giving you a separate IP address on the local network, neither of which you seem to need.
n
I have a sinking suspicion it's related to https://pierce.dev/notes/local-network-config-on-macos but I'll restart w/o that and give it another shot
f
Maybe, but a naïve test failed for me here as well. Please open a GitHub issue, and we'll look into it (it is a holiday here today).
n
I will. Thanks for your time!
Well, and of course... I'v spent a few hours on it, restarted the machine, reinstalled RD a couple times, even went through making a slack account then I try to reproduce it again to copy-paste logs into GH ... it works perfectly and I can't trigger it again