Open kdandersen opened 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
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
@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 :(
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
Hi @philippe-granet
You workaround works! 👍
Thanks for sharing
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
Please, note that Rancher Desktop has an installer proposing a User install. But I fear it is a completely different packager.
@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
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.
Yes you got that right, I thought you want to release the GUI .exe
alongside the .msi
Please allow DevPod to be installed in users App\Local or similar location, not requiring local admin privileges or elevation on Windows.