The tested constraint for Docker Desktop in config.yml is currently set to <=4.37.99:
dockerSupportedVersions:
desktop:
tested: "<=4.37.99"
The latest Docker Desktop release satisfying this constraint is 4.37.2, released on 2025-01-09. Any newer version causes Lando to display the following notice on every lando start:
ℹ Using an untested version of DOCKER DESKTOP
We have not tested version 4.80.0 yet so congrats on being a pioneer!
Seriously though, this is usually not an issue but be mindful that you
are in uncharted territory. If you encounter an issue we recomend
you downgrade to something <=4.37.99.
This means users running an up-to-date Docker Desktop are actively advised to downgrade to an eighteen-month-old release, one that predates all security fixes shipped since January 2025.
Expected behaviour:
The tested constraint is kept up to date so that users running current Docker Desktop versions are not discouraged from doing so.
Suggested fix:
Update tested to reflect a recent Docker Desktop version, and establish a process, such as a periodic reminder or automated check, to keep this value current with Docker Desktop releases.
Security note:
In the current threat landscape, where supply chain attacks explicitly target developer workstations and their credentials, discouraging users from keeping Docker Desktop up to date is a security concern that goes beyond cosmetics.
The tested constraint for Docker Desktop in
config.ymlis currently set to<=4.37.99:The latest Docker Desktop release satisfying this constraint is 4.37.2, released on 2025-01-09. Any newer version causes Lando to display the following notice on every
lando start:This means users running an up-to-date Docker Desktop are actively advised to downgrade to an eighteen-month-old release, one that predates all security fixes shipped since January 2025.
Expected behaviour:
The
testedconstraint is kept up to date so that users running current Docker Desktop versions are not discouraged from doing so.Suggested fix:
Update
testedto reflect a recent Docker Desktop version, and establish a process, such as a periodic reminder or automated check, to keep this value current with Docker Desktop releases.Security note:
In the current threat landscape, where supply chain attacks explicitly target developer workstations and their credentials, discouraging users from keeping Docker Desktop up to date is a security concern that goes beyond cosmetics.