A JavaScript error occurred in the main process

rancher-sandbox / rancher-desktop

Container Management and Kubernetes on the Desktop

https://rancherdesktop.io

Apache License 2.0

6.01k stars 283 forks source link

A JavaScript error occurred in the main process #7525

Open GlenHughes opened 1 month ago

GlenHughes commented 1 month ago

Actual Behavior

Getting a constant error alert. When closing a new error opens and repeats.

Steps to Reproduce

Open Rancher Desktop

Result

Expected Behavior

Should be able to use the application

Additional Information

No response

Rancher Desktop Version

1.15.1

Rancher Desktop K8s Version

Not sure can't check

Which container engine are you using?

containerd (nerdctl)

What operating system are you using?

Windows

Operating System / Build Version

Windows 10 Pro Version 10.0.19045 Build 19045

What CPU architecture are you using?

x64

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

None

Windows User Only

No response

mook-as commented 1 month ago

Hi! Sorry about that. Would you be able to attach all of the logs to help us see what's going on? If you can't interact with Rancher Desktop right now, you can also open Windows Explorer and attach the files from C:\Users\Glen_\AppData\Local\rancher-desktop\logs.

Did you try to install an extension before this happened?

GlenHughes commented 1 month ago

No worries - logs attached.

logs.zip

mook-as commented 1 month ago

Thanks! Unfortunately, that didn't seem to contain anything related to the error (which probably means we didn't log it correctly). But it looks like the issue is with the dive-in extension; however, that seems to work fine on my Windows machine.

Do you recall what you were doing at the time this error showed up?
To double check, are you an administrator on this machine? (You shouldn't need to be; I'm trying to narrow down the issues.)
Would you be able to re-capture the logs with debug logging enabled? That might give us more clues…

My current best guess is that we're extracting the whole docker image to the host (because the extension's docker compose file is at the root, and we don't know what files it would need). Something is falling over trying to extract /bin/cat. But we don't do symlinks on Windows (we dereference everything instead), so that normally wouldn't be an issue… unless your anti-virus didn't like having a copy of Linux busybox?