
Log4j 2 CVE-2021-44228: We have updated the docker scan CLI plugin for you. This new version of docker scan is able to detect Log4j 2įor more information, read the blog post Apache Log4j 2 Log4j 2 CVE-2021-44228: We have updated the docker scan CLI plugin. Gaining access to this data would require having access to the user’s local files. This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user has logged in while on 4.3.0, 4.3.1.


Disabled Dashboard shortcuts to prevent capturing them even when minimized or un-focussed.Doing a Reset to factory defaults no longer shuts down Docker Desktop.Fixed a regression in Compose that reverted the container name separator from - to _.If you are using multiple organizations for different groups of developers, you must provision a separate registry.json file for each group. Docker Desktop displays an error if registry.json contains more than one organization in the allowedOrgs field.Signing in to Docker Desktop now takes you through the browser so that you get all the benefits of auto-filling from password managers.For more information, see Single Sign-on.

Single Sign-on: Users with a Docker Business subscription can now configure SSO to authenticate using their identity providers (IdPs) to access Docker.Easy, Secure sign in with Auth0 and Single Sign-on.Fixed CVE-2021-45449 that affects users currently on Docker Desktop version 4.3.0 or 4.3.1.ĭocker Desktop version 4.3.0 and 4.3.1 has a bug that may log sensitive information (access token or password) on the user’s machine during login.

Take a look at the Docker Public Roadmap to see what’s coming next. This page contains information about the new features, improvements, known issues, and bug fixes in Docker Desktop releases. The grace period for those that will require a paid subscription Commercial use of Docker Desktop in larger enterprises (more than 250Įmployees OR more than $10 million USD in annual revenue) now requires a paid
