Docker Desktop 2.2.0.0: Shared Files, Known Issues, Upgrades, and New Features

- Fixed a bug where running the command `DockerCli.exe -SharedDrives` failed to display a list of drives that are shared. Fixes [docker/for-win#5625](https://github.com/docker/for-win/issues/5625). - Starting with Docker Desktop 2.2.0.3, you must access all shared files using their original case. For example, if you have created a file called `test`, you must open it as `test`. Attempts to open the file as `Test` will fail with the error `No such file or directory`. For more information, see _Tips on shared drives, permissions, and volume mounts_ in [File sharing](/manuals/desktop/settings-and-maintenance/settings.md#file-sharing). ### Known issues - DockerNAT has been removed from Docker Desktop 2.2.0.0 as using an IP address to communicate from the host to a container is not a supported feature. To communicate from a container to the host, you must use the special DNS name `host.docker.internal`. We also recommend using ports to communicate from the host to a container. For more information, see [Networking](/manuals/desktop/features/networking.md#use-cases-and-workarounds-for-all-platforms). However, if your current setup relies on IP addresses for communication, you can use a temporary workaround to reinstate DockerNAT. To do this, open `C:\Program Files\Docker\Docker\resources\MobyLinux.ps1` and add `$SwitchName = "DockerNAT"` between line 175 and 176. Note that the temporary workaround to reinstate DockerNAT may be removed from future releases. - Directory junctions in shared volumes pointing outside the shared volume do not work. - It is currently not possible to rename open files within shared volumes. - In some cases, Docker containers do not synchronize time with the host when the host machine is put to sleep. - It is not possible to use `localhost` in the proxy settings. You can instead use `host.docker.internal` to work around this issue. ## Docker Desktop Community 2.2.0.0 2020-01-21 Docker Desktop 2.2.0.0 contains a Kubernetes upgrade. Your local Kubernetes cluster will be reset after installing this version. ### Upgrades - [Docker Compose 1.25.2](https://github.com/docker/compose/releases/tag/1.25.2) - [Kubernetes 1.15.5](https://github.com/kubernetes/kubernetes/releases/tag/v1.15.5) - Linux kernel 4.19.76 - [QEMU 4.0.1](https://github.com/docker/binfmt) ### New - **Docker Desktop Dashboard:** The new Docker Desktop **Dashboard** provides a user-friendly interface which enables you to interact with containers and applications, and manage the lifecycle of your applications directly from the UI. In addition, it allows you to access the logs, view container details, and monitor resource utilization to explore the container behavior. For detailed information about the new Dashboard UI, see [Docker Desktop Dashboard](../_index.md). - **WSL 2 backend:** The experimental Docker Desktop WSL 2 backend architecture introduces support for Kubernetes, provides an updated Docker daemon, offers VPN-friendly networking, and additional features. For more information, see [Docker Desktop WSL 2 backend](/manuals/desktop/features/wsl/_index.md). - **New file sharing implementation:** Docker Desktop introduces a new file sharing implementation that replaces Samba, CIFS, and Hyper-V networking. The new implementation offers improved I/O performance. Additionally, when using the new file system: - Users don't have to expose the Samba port, and therefore do not experience issues related to IT firewall or drive-sharing policy. - There is no need to provide user credentials to Docker Desktop. File access rights are automatically enforced when accessing mounted folders through containers. For more information, see the blog post [New file sharing implementation in Docker Desktop Windows](https://www.docker.com/blog/new-filesharing-implementation-in-docker-desktop-windows/). - Added the **WSL Integration** option in **Settings** > **Resources** to select WSL 2 distributions. This option will be visible only after enabling WSL 2 on your machine.

Docker Desktop 2.2.0.0 fixes a bug where `DockerCli.exe -SharedDrives` failed, enforces case-sensitive file access in shared volumes, and removes DockerNAT (with a temporary workaround provided). Known issues include directory junctions and open file renaming limitations in shared volumes, container time synchronization problems after host sleep, and `localhost` proxy setting issues. The release includes upgrades to Docker Compose, Kubernetes, the Linux kernel, and QEMU. New features comprise the Docker Desktop Dashboard for container management, experimental WSL 2 backend for Kubernetes support and improved networking, and a new file sharing implementation with improved I/O performance and enhanced security. A WSL Integration option in settings allows selecting WSL 2 distributions.