Installer requires elevation - which you can safely and securely do yourself, Docker

Docker Desktop
,
1

Every time a new Docker Desktop comes out, I go to install the update and get:

fork/exec C:\Users\heaths\AppData\Local\Temp\DockerDesktopUpdates\Docker Desktop Installer (220185).exe: The requested operation requires elevation.

It’s entirely possible for you to elevate yourself. If you have a separate process that runs outside the installation folder so that you can update the app, use ShellExecuteEx with the “runas” verb. If you want more security and control, take a look at how the Windows Installer XML toolchain’s burn works. I helped on the elevation story there as well as subsequent hardening when a DLL injection attack was discovered in all LoadLibrary calls on Windows, but the version I worked on and know is older: GitHub - wixtoolset/wix3: WiX Toolset v3.x · GitHub.

It’s not difficult, but what is for most consumers is working around this problem when Docker Desktop is installed and run as a non-elevated user (which anyone should be!). Please do better.

2

Thanks for your idea! Could you also share it in the roadmap?

Or there is also a desktop-feedback github repo for Docker Desktop issues

I think both would be okay in this case.

This is a community forum and Docker Staff members can be seen here from time to time, but if you want to make sure they see your advice, the mentioned github repos are direct channels to them. I could not really add useful comments to this topic unfortunately.