`Docker.DockerDesktop` 4.74.0 adds new custom installer arguments that break interactive install

[dhmjhu]

The Docker.DockerDesktop 4.74.0 manifest added in #376651 introduced new Custom installer arguments --accept-license --backend=wsl-2 --no-windows-containers.

winget-pkgs/manifests/d/Docker/DockerDesktop/4.74.0/Docker.DockerDesktop.installer.yaml

Line 16 in 53d2ac7

Custom: --accept-license --backend=wsl-2 --no-windows-containers

These arguments do not appear in previous versions. (Compare 4.73.0.) If there was any discussion or rationale for this change, I can't find it.

This change caused interactive installation to break as described in #381599. (When command-line options are provided, the installer requires an explicit command such like install.)

PR #381609 works around the issue by adding Interactive: install, but it is unclear why these custom arguments were needed in the first place.

In particular, I'm not sure these options should be forced by the package manifest, as they appear to change Docker Desktop configuration/behavior.

[Paciupa]

I had exact this problem and question, did you check out Docker Desktop installer doc? As I understand these flags allow really quiet installation and make most common choices default; custom because Docker Desktop Installer is custom, not some MSI or Inno Setup.

• --accept-license: skips license step
• --backend=wsl-2: wsl-2 is default by Docker itself and most common
• --no-windows-containers: linux containers are also default by docker. more info

[dhmjhu]

I understand what the flags do; my concern is that the manifest is forcing those choices at all.

A non-interactive install is already silent because WinGet passes --quiet, and the installer uses its own defaults.

I don't think it is appropriate for a WinGet manifest to override installer defaults unless there is a specific technical reason to do so. I expect WinGet to install software using the vendor's defaults, not to impose additional configuration choices.

The reason I'm doing an interactive install is to configure it myself.

I'm also surprised the manifest is automatically passing --accept-license, especially for interactive installs.