https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
h
try rebooting the computer. there are likely zombie processes lying around. I'm having a lot of trouble with getting it working too By The Way.
g
Been there, done that. šŸ˜
h
I also blew away the following directories: .docker .kube .kuberlr (sp?) ~/Library/Application Support/Rancher Desktop ~/Library/Caches/(anything with rancher)
And delete rancher desktop and re-install
g
Not willing to blow away my .kube directory because not everything is Rancher Desktopā€¦
h
fair enough... maybe just save it then?
c
You should be able to find your logs on macOS under 
~/Library/Logs/rancher-desktop
I donā€™t think the team is aware of such an issue like this, so it would be beneficial if youā€™re able to gather details and raise an issue
g
Ok, will do
šŸ™Œ 1
what the heck is this?
Copy code
2023-08-17T16:04:15.648Z: Still processing the first-run dialog: not opening main window
2023-08-17T16:04:18.564Z: Error starting up: SystemError [ERR_FS_EISDIR]: Path is a directory: rm returned EISDIR (is a directory) /Users/rpatrick/.rd/bin/jms-cluster-models
    at new SystemError (node:internal/errors:234:5)
    at new NodeError (node:internal/errors:337:7)
    at node:internal/fs/utils:781:17
    at FSReqCallback.oncomplete (node:fs:199:5) {
  code: 'ERR_FS_EISDIR',
  info: {
    code: 'EISDIR',
    message: 'is a directory',
    path: '/Users/rpatrick/.rd/bin/jms-cluster-models',
    syscall: 'rm',
    errno: 21
  },
  errno: [Getter/Setter: 21],
  syscall: [Getter/Setter: 'rm'],
  path: [Getter/Setter: '/Users/rpatrick/.rd/bin/jms-cluster-models']
}
@curved-zebra-30454 I figured out the problem. I had mistakenly saved a directory in $HOME/.rd/bin and for some reason unbeknownst top me, Rancher Desktop was trying to process that directory at startupā€¦probably not the best ideaā€¦. šŸ˜ž
After fixing and reinstalling everything, I now get the following when trying to do a docker build:
Copy code
Build command failed with error: docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown.
c
Do you get this error for only a specific docker image that you try to build?
g
not sure, only need to build this one image right now
c
are you able to provide an example?
g
maybeā€¦
any idea what is going on with this?
Copy code
rpatrick@rpatrick-mac ~ % docker images
REPOSITORY                                          TAG       IMAGE ID       CREATED         SIZE
<http://ghcr.io/rancher-sandbox/rancher-desktop/rdx-proxy|ghcr.io/rancher-sandbox/rancher-desktop/rdx-proxy>   latest    244de06018b1   292 years ago   5.1MB
pretty sure the image is not 292 years old
seems to be corrupt?
c
I'm not sure why it's 292 years old, but I'm seeing the same on two functioning instances, so I just created an issue for it https://github.com/rancher-sandbox/rancher-desktop/issues/5360
Scratch that, this issue is known and will be addressed in the 1.10 release https://github.com/rancher-sandbox/rancher-desktop/issues/5145
g
turns out the problem was that somehow, my busybox image in my local cache was corruptedā€¦once I deleted and pulled a fresh image, the problem went away
šŸ¤” 1
334 Views
Open in Slack
PreviousNext
Powered by