Docker Desktop

For managed Docker Desktop updates, close the desktop application before starting the installer. If the app is left running, the update can fail or leave the install in an untrustworthy state: the MSI update can fail with <code>Exit Code 1</code> when Docker Desktop is open. Add a pre-close/check step for the app process in deployment tooling before retrying the update.

Official source: Docker Desktop official download/source page.

For managed Docker Desktop installs, choose the install scope explicitly. Docker documents per-user installs with "Docker Desktop Installer.exe" install --user and all-users installs with "Docker Desktop Installer.exe" install from an elevated context. For noninteractive acceptance, include --accept-license where appropriate. After an all-users install, make sure intended users are in the local docker-users group before expecting Hyper-V/Windows-container features to work.

Source: Docker Desktop official documentation.

Close Docker Desktop before managed upgrades. Leaving Docker Desktop running can cause update failures or leave services and application files in a partially updated state; verify Docker Desktop starts cleanly after deployment. Source: official Docker Desktop source.

For Docker Desktop packaging, use Docker’s official Windows installation/download documentation as the source of record and stage the installer in a local content repository before assignment. If an older packaging host cannot fetch the current Docker Desktop installer directly, replace the binary manually and record the staged version/hash rather than silently reusing an older cached installer.

Source: Docker Desktop official documentation.