Error installing Epinio on Windows

[mook-as]

Actual Behavior

When attempting to install Epinio, we end up with an error:

Steps to Reproduce

1. Start Rancher Desktop
2. Install the Epinio extension
3. Install Epinio from the extension

Result

Error message pops up.

Expected Behavior

Epinio is installed

Additional Information

Probably relevant line in the logs:

2024-07-30T19:26:34.188Z: ipcMain: "extensions/spawn/blocking" handle called with: {"command":["epinio-http.bat"],"execId":"ddaa54ec9fa5f08fb3ed5bc39b2d7b30-host-20","scope":"host"}

I don't think spawning batch files have worked since one of the Electron updates. See 4e850ab

Rancher Desktop Version

1.15.0-rc1 88b962c

Rancher Desktop K8s Version

1.29.6

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 11 Pro 23H2 (Build 22631.3880)

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

[krumware]

👋 Can a project maintainer please assign this to me?
related to: epinio/extension-docker-desktop#66

[krumware]

Hi @mook-as, some questions. Was the Epinio extension installed prior to updating to 1.15, or is this a fresh install.
Also, what was the installation method you used (for the extension in general, not for the "Install/Upgrade" mentioned in this step)? rdctl or via UI?

Thanks!

[mook-as]

This was a fresh install, installing from the Rancher Desktop built-in available extensions list in the UI.

See 4e850ab as mentioned in the Additional Information section — during an Electron update, it's been changed so that we can't directly spawn *.bat / *.cmd file anymore. I believe a possible fix is on the Rancher Desktop side to unshift cmd.exe /c in front of the command line (so that it works around the security restriction).

Another option is for the Epinio extension to use an .exe file instead of a .bat.