loft-sh / devpod

Codespaces but open-source, client-only and unopinionated: Works with any IDE and lets you use any cloud, kubernetes or just localhost docker.
https://devpod.sh
Mozilla Public License 2.0
9.01k stars 336 forks source link

Please allow installation of DevPod Windows UI without requiring local admin privileges #392

Open kdandersen opened 1 year ago

kdandersen commented 1 year ago

Please allow DevPod to be installed in users App\Local or similar location, not requiring local admin privileges or elevation on Windows.

pascalbreuninger commented 1 year ago

Hi @kdandersen, thank you for opening the issue. We looked into the topic a while ago but tbh it's not very high up on the priority list. You can try to work around it using msiexec, see our slack channel for more information on that

kdandersen commented 1 year ago

Hmm,

Gave it a try with command:

msiexec /i "DevPod_windows_x64_en-US.msi" ALLUSERS="" INSTALLDIR=%LOCALAPPDATA%/Programs/DevPod

But still required elevation.

Anyhow, thanks for suggesting.

Rgds

philippe-granet commented 1 year ago

@pascalbreuninger same problem, many companies impose restrictions on their PC and disable local admin privileges or elevation on Windows for security reasons.
It's my case, and I can't test devpod :(

philippe-granet commented 1 year ago

I found a work around.
Extract the msi: msiexec /a DevPod_windows_x64_en-US.msi /qb TARGETDIR=c:\devpod
Then you find DevPod.exe in C:\devpod\PFiles\DevPod and can launch it without local admin privileges or elevation

kdandersen commented 1 year ago

Hi @philippe-granet

You workaround works! 👍

Thanks for sharing

gbonnefille commented 11 months ago

If so, what about releasing the .exe alone, near to the .msi? I'm not so sure where the .exe is before releasing it. https://github.com/loft-sh/devpod/blob/8417972dcdb78e8c0145e587ee36de34636d6046/.github/workflows/release.yaml#L307

gbonnefille commented 11 months ago

Please, note that Rancher Desktop has an installer proposing a User install. But I fear it is a completely different packager.

pascalbreuninger commented 11 months ago

@gbonnefille I fear if we just release the .exe file it will be more confusing to figure out which file to download and I'm not sure if the signing will still work without the msi. Long-term we should adjust the installer to allow for user installs

gbonnefille commented 11 months ago

I certainly misunderstood something, but the .exe I found in the Releases is the cli only.

In order to have a GUI running, I had to disassemble the .msi and run the Path executable.

pascalbreuninger commented 11 months ago

Yes you got that right, I thought you want to release the GUI .exe alongside the .msi