mirror of https://github.com/docker/docs.git
Move 'Previous Versions' into new folder at root of DD docs (#14742)
* moveed previous versions into new folder at root of DD docs * fix broken links * fix broken links * broken link fix
This commit is contained in:
Allie Sadler
GitHub
parent
861e079559
commit
59203dd95c
|
|
@ -1194,16 +1194,6 @@ manuals:
|
|||
title: Logs and troubleshooting
|
||||
- path: /desktop/mac/apple-silicon/
|
||||
title: Apple silicon
|
||||
- sectiontitle: Previous versions
|
||||
section:
|
||||
- path: /desktop/mac/release-notes/3.x/
|
||||
title: Desktop for Mac 3.x
|
||||
- path: /desktop/mac/release-notes/2.x/
|
||||
title: Desktop for Mac 2.x
|
||||
- path: /desktop/mac/release-notes/edge-releases/
|
||||
title: Edge releases
|
||||
- path: /desktop/mac/release-notes/archive/
|
||||
title: Older versions
|
||||
- sectiontitle: Windows
|
||||
section:
|
||||
- path: /desktop/windows/install/
|
||||
|
|
@ -1216,16 +1206,6 @@ manuals:
|
|||
title: Logs and troubleshooting
|
||||
- path: /desktop/windows/wsl/
|
||||
title: Docker Desktop WSL 2 backend
|
||||
- sectiontitle: Previous versions
|
||||
section:
|
||||
- path: /desktop/windows/release-notes/3.x/
|
||||
title: Desktop for Windows 3.x
|
||||
- path: /desktop/windows/release-notes/2.x/
|
||||
title: Desktop for Windows 2.x
|
||||
- path: /desktop/windows/release-notes/edge-releases/
|
||||
title: Edge releases
|
||||
- path: /desktop/windows/release-notes/archive/
|
||||
title: Older versions
|
||||
- sectiontitle: Linux
|
||||
section:
|
||||
- path: /desktop/linux/install/
|
||||
|
|
@ -1324,9 +1304,26 @@ manuals:
|
|||
title: FAQs
|
||||
- path: /desktop/backup-and-restore/
|
||||
title: Back up and restore data
|
||||
- sectiontitle: Previous versions
|
||||
section:
|
||||
- path: /desktop/previous-versions/3.x-windows/
|
||||
title: Desktop for Windows 3.x
|
||||
- path: /desktop/previous-versions/3.x-mac/
|
||||
title: Desktop for Mac 3.x
|
||||
- path: /desktop/previous-versions/2.x-windows/
|
||||
title: Desktop for Windows 2.x
|
||||
- path: /desktop/previous-versions/2.x-mac/
|
||||
title: Desktop for Mac 2.x
|
||||
- path: /desktop/previous-versions/edge-releases-windows/
|
||||
title: Windows edge releases
|
||||
- path: /desktop/previous-versions/edge-releases-mac/
|
||||
title: Mac edge releases
|
||||
- path: /desktop/previous-versions/archive-windows/
|
||||
title: Older versions for Windows
|
||||
- path: /desktop/previous-versions/archive-mac/
|
||||
title: Older versions for Mac
|
||||
- path: /desktop/release-notes/
|
||||
title: Release notes
|
||||
|
||||
- sectiontitle: Docker Engine
|
||||
section:
|
||||
- path: /engine/
|
||||
|
|
|
|||
|
|
@ -4,6 +4,7 @@ keywords: Docker Desktop for Mac 2.x release notes
|
|||
title: Docker Desktop for Mac 2.x release notes
|
||||
toc_min: 1
|
||||
toc_max: 2
|
||||
redirect_from: /desktop/mac/release-notes/2.x/
|
||||
---
|
||||
|
||||
This page contains release notes for Docker Desktop for Mac 2.x.
|
||||
|
|
@ -290,7 +291,7 @@ Docker Desktop 2.2.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
### 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](../../dashboard.md).
|
||||
For detailed information about the new Dashboard UI, see [Docker Desktop Dashboard](../dashboard.md).
|
||||
|
||||
- Introduced a new user interface for the Docker Desktop **Preferences** menu.
|
||||
- The Restart, Reset, and Uninstall options are now available on the **Troubleshoot** menu.
|
||||
|
|
@ -358,7 +359,7 @@ Docker Desktop 2.1.0.5 contains a Kubernetes upgrade. Note that your local Kuber
|
|||
### New
|
||||
|
||||
Docker Desktop now enables you to sign into Docker Hub using two-factor authentication.
|
||||
For more information, see [Two-factor authentication](../index.md#docker-hub).
|
||||
For more information, see [Two-factor authentication](../mac/index.md#docker-hub).
|
||||
|
||||
## Docker Desktop Community 2.1.0.3
|
||||
2019-09-16
|
||||
|
|
@ -4,6 +4,7 @@ keywords: Docker Desktop for Windows 2.x, release notes
|
|||
title: Docker for Windows 2.x release notes
|
||||
toc_min: 1
|
||||
toc_max: 2
|
||||
redirect_from: /desktop/windows/release-notes/2.x/
|
||||
---
|
||||
|
||||
This page contains release notes for Docker Desktop for Windows 2.x.
|
||||
|
|
@ -229,7 +230,7 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
|
||||
### New
|
||||
|
||||
- Windows 10 Home users can now use Docker Desktop through WSL 2. This requires Windows 10, version 2004 or higher. For more information, see [Install Docker Desktop on Windows](../install.md).
|
||||
- Windows 10 Home users can now use Docker Desktop through WSL 2. This requires Windows 10, version 2004 or higher. For more information, see [Install Docker Desktop on Windows](../windows/install.md).
|
||||
- Docker Desktop introduces a new onboarding tutorial upon first startup. The Quick Start tutorial guides users to get started with Docker in a few easy steps. It includes a simple exercise to build an example Docker image, run it as a container, push and save the image to Docker Hub.
|
||||
- Docker Desktop now allows sharing individual folders, rather than whole drives, giving more control to users over what is being shared.
|
||||
|
||||
|
|
@ -284,7 +285,7 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
|
||||
### Known issues
|
||||
|
||||
- Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the [WSL 2 backend](../wsl.md).
|
||||
- Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the [WSL 2 backend](../windows/wsl.md).
|
||||
|
||||
**WSL 2**
|
||||
|
||||
|
|
@ -336,7 +337,7 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
|
||||
### Known issues
|
||||
|
||||
- Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the experimental [WSL backend](../wsl.md).
|
||||
- Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the experimental [WSL backend](../windows/wsl.md).
|
||||
- It is not possible to resize the disk image using the Docker Desktop **Settings** UI. If you would like to update the size of the disk image (for example, to 128 GB), run the following command in PowerShell:
|
||||
|
||||
```powershell
|
||||
|
|
@ -376,11 +377,11 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
- Fixed a race condition when starting the WSL engine which caused Docker Desktop to incorrectly report that the containers have exited. Fixes [docker/for-win#5607](https://github.com/docker/for-win/issues/5607).
|
||||
- Fixed an issue where editing code inside a container resulted in an error. Fixes [docker/for-win#5528](https://github.com/docker/for-win/issues/5528).
|
||||
- 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](../index.md#file-sharing).
|
||||
- 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](../windows/index.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](../networking.md#use-cases-and-workarounds).
|
||||
- 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](../windows/networking.md#use-cases-and-workarounds).
|
||||
|
||||
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.
|
||||
|
|
@ -404,9 +405,9 @@ Docker Desktop 2.2.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
### 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](../../dashboard.md).
|
||||
For detailed information about the new Dashboard UI, see [Docker Desktop Dashboard](../dashboard.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](../wsl.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](../windows/wsl.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:
|
||||
|
||||
|
|
@ -486,7 +487,7 @@ Docker Desktop 2.1.0.4 contains a Kubernetes upgrade. Note that your local Kuber
|
|||
|
||||
### New
|
||||
|
||||
Docker Desktop now enables you to sign into Docker Hub using two-factor authentication. For more information, see [Two-factor authentication](../index.md#two-factor-authentication).
|
||||
Docker Desktop now enables you to sign into Docker Hub using two-factor authentication. For more information, see [Two-factor authentication](../windows/index.md#two-factor-authentication).
|
||||
|
||||
## Docker Desktop Community 2.1.0.3
|
||||
2019-09-16
|
||||
|
|
@ -7,6 +7,7 @@ toc_max: 2
|
|||
redirect_from:
|
||||
- /desktop/mac/previous-versions/
|
||||
- /docker-for-mac/previous-versions/
|
||||
- /desktop/mac/release-notes/3.x/
|
||||
---
|
||||
|
||||
This page contains release notes for Docker Desktop for Mac 3.x.
|
||||
|
|
@ -34,8 +35,8 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
- **Dev Environments**: You can now create a Dev Environment from your local Git repository. For more information, see [Start a Dev Environment from a local folder](../../dev-environments.md#start-a-dev-environment-from-a-local-folder).
|
||||
- **Volume Management**: You can now sort volumes by the name, the date created, and the size of the volume. You can also search for specific volumes using the **Search** field. For more information, see [Explore volumes](../../dashboard.md#explore-volumes).
|
||||
- **Dev Environments**: You can now create a Dev Environment from your local Git repository. For more information, see [Start a Dev Environment from a local folder](../dev-environments.md#start-a-dev-environment-from-a-local-folder).
|
||||
- **Volume Management**: You can now sort volumes by the name, the date created, and the size of the volume. You can also search for specific volumes using the **Search** field. For more information, see [Explore volumes](../dashboard.md#explore-volumes).
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -72,7 +73,7 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../../dev-environments.md).
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments.md).
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -107,9 +108,9 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../../dev-environments.md).
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
### Bug fixes and minor changes
|
||||
|
||||
|
|
@ -127,9 +128,9 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../../dev-environments.md).
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -166,15 +167,15 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../../dashboard.md#explore-volumes).
|
||||
**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../dashboard.md#explore-volumes).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
**Skip Docker Desktop updates**: All users can now skip an update when they are prompted to install individual Docker Desktop releases. For more information, see [Docker Desktop updates](../../windows/install.md#updates).
|
||||
**Skip Docker Desktop updates**: All users can now skip an update when they are prompted to install individual Docker Desktop releases. For more information, see [Docker Desktop updates](../windows/install.md#updates).
|
||||
|
||||
### Deprecation
|
||||
|
||||
- Docker Desktop no longer installs Notary. You can now use [Docker Content Trust](../../../engine/security/trust/index.md) for image signing.
|
||||
- Docker Desktop no longer installs Notary. You can now use [Docker Content Trust](../../engine/security/trust/index.md) for image signing.
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -267,7 +268,7 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
Docker Desktop is now available for Apple silicon as well as Intel chips. This enables developers with their choice of local development environments, and extends development pipelines for ARM-based applications. For more information, see [Docker Desktop for Apple silicon](../apple-silicon.md).
|
||||
Docker Desktop is now available for Apple silicon as well as Intel chips. This enables developers with their choice of local development environments, and extends development pipelines for ARM-based applications. For more information, see [Docker Desktop for Apple silicon](../mac/apple-silicon.md).
|
||||
|
||||
### Bug fixes and minor changes
|
||||
|
||||
|
|
@ -520,7 +521,7 @@ Docker Desktop can sometimes fail to start after updating to version 3.2.0. If y
|
|||
### New
|
||||
|
||||
- Use of three-digit version number for Docker Desktop releases.
|
||||
- Starting with Docker Desktop 3.0.0, updates are now much smaller as they will be applied using delta patches. For more information, see [Automatic updates](../install.md#updates).
|
||||
- Starting with Docker Desktop 3.0.0, updates are now much smaller as they will be applied using delta patches. For more information, see [Automatic updates](../mac/install.md#updates).
|
||||
- First version of `docker compose` (as an alternative to the existing `docker-compose`). Supports some basic commands but not the complete functionality of `docker-compose` yet.
|
||||
|
||||
- Supports the following subcommands: `up`, `down`, `logs`, `build`, `pull`, `push`, `ls`, `ps`
|
||||
|
|
@ -7,6 +7,7 @@ toc_max: 2
|
|||
redirect_from:
|
||||
- /desktop/windows/previous-versions/
|
||||
- /docker-for-windows/previous-versions/
|
||||
- /desktop/windows/release-notes/3.x/
|
||||
---
|
||||
|
||||
This page contains release notes for Docker Desktop for Windows 3.x.
|
||||
|
|
@ -33,8 +34,8 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
- **Dev Environments**: You can now create a Dev Environment from your local Git repository. For more information, see [Start a Dev Environment from a local folder](../../dev-environments.md#start-a-dev-environment-from-a-local-folder).
|
||||
- **Volume Management**: You can now sort volumes by the name, the date created, and the size of the volume. You can also search for specific volumes using the **Search** field. For more information, see [Explore volumes](../../dashboard.md#explore-volumes).
|
||||
- **Dev Environments**: You can now create a Dev Environment from your local Git repository. For more information, see [Start a Dev Environment from a local folder](../dev-environments.md#start-a-dev-environment-from-a-local-folder).
|
||||
- **Volume Management**: You can now sort volumes by the name, the date created, and the size of the volume. You can also search for specific volumes using the **Search** field. For more information, see [Explore volumes](../dashboard.md#explore-volumes).
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -77,7 +78,7 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../../dev-environments.md).
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments.md).
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -111,9 +112,9 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../../dev-environments.md).
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
### Bug fixes and minor changes
|
||||
|
||||
|
|
@ -131,9 +132,9 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../../dev-environments.md).
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -168,11 +169,11 @@ This page contains information about the new features, improvements, known issue
|
|||
|
||||
### New
|
||||
|
||||
**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../../dashboard.md#explore-volumes).
|
||||
**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../dashboard.md#explore-volumes).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
**Skip Docker Desktop updates**: All users can now skip an update when they are prompted to install individual Docker Desktop releases. For more information, see [Docker Desktop updates](../install.md#updates).
|
||||
**Skip Docker Desktop updates**: All users can now skip an update when they are prompted to install individual Docker Desktop releases. For more information, see [Docker Desktop updates](../windows/install.md#updates).
|
||||
|
||||
### Deprecation
|
||||
|
||||
|
|
@ -424,7 +425,7 @@ For developers in IT managed environments, who don’t have administrative acces
|
|||
### New
|
||||
|
||||
- Use of three-digit version number for Docker Desktop releases.
|
||||
- Docker Desktop updates are now much smaller as they will be applied using delta patches. For more information, see [Automatic updates](../install.md#updates).
|
||||
- Docker Desktop updates are now much smaller as they will be applied using delta patches. For more information, see [Automatic updates](../windows/install.md#updates).
|
||||
- First version of `docker compose` (as an alternative to the existing `docker-compose`). Supports some basic commands but not the complete functionality of `docker-compose` yet.
|
||||
|
||||
- Supports the following subcommands: `up`, `down`, `logs`, `build`, `pull`, `push`, `ls`, `ps`
|
||||
|
|
@ -4,6 +4,8 @@ keywords: Docker Desktop for Mac, release notes
|
|||
title: Release notes for previous versions
|
||||
toc_min: 1
|
||||
toc_max: 2
|
||||
redirect_from:
|
||||
- /desktop/mac/release-notes/archive/
|
||||
---
|
||||
|
||||
This page contains release notes for older versions of Docker Desktop for Mac.
|
||||
|
|
@ -40,7 +42,7 @@ This page contains release notes for older versions of Docker Desktop for Mac.
|
|||
- Linux Kernel 4.9.93 with CEPH, DRBD, RBD, MPLS_ROUTING and MPLS_IPTUNNEL enabled
|
||||
|
||||
* New
|
||||
- Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker For Mac Preferences and use kubectl commands as well as docker commands. See [the Kubernetes section](../../kubernetes.md)
|
||||
- Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker For Mac Preferences and use kubectl commands as well as docker commands. See [the Kubernetes section](../kubernetes.md)
|
||||
- Add an experimental SOCKS server to allow access to container networks, see [docker/for-mac#2670](https://github.com/docker/for-mac/issues/2670#issuecomment-372365274). Also see [docker/for-mac#2721](https://github.com/docker/for-mac/issues/2721)
|
||||
- Re-enable raw as the default disk format for users running macOS 10.13.4 and higher. Note this change only takes effect after a "reset to factory defaults" or "remove all data" (from the Whale menu -> Preferences -> Reset). Related to [docker/for-mac#2625](https://github.com/docker/for-mac/issues/2625)
|
||||
|
||||
|
|
@ -132,7 +134,7 @@ This page contains release notes for older versions of Docker Desktop for Mac.
|
|||
- Clearer error message when incompatible hardware is detected.
|
||||
- Fix some cases where selecting "Reset" after an error did not reset properly.
|
||||
- Fix incorrect NTP config. Fixes [docker/for-mac#2529](https://github.com/docker/for-mac/issues/2529)
|
||||
- Migration of Docker Toolbox images is not proposed anymore in Docker For Mac installer (still possible to [migrate Toolbox images manually](../../../toolbox/index.md)).
|
||||
- Migration of Docker Toolbox images is not proposed anymore in Docker For Mac installer (still possible to migrate Toolbox images manually).
|
||||
|
||||
### Docker Community Edition 17.12.0-ce-mac55 2018-02-27
|
||||
|
||||
|
|
@ -193,7 +195,7 @@ This page contains release notes for older versions of Docker Desktop for Mac.
|
|||
- VM entirely built with Linuxkit
|
||||
- VM disk size can be changed in disk preferences. (See [docker/for-mac#1037](https://github.com/docker/for-mac/issues/1037))
|
||||
- For systems running APFS on SSD on High Sierra, use `raw` format VM disks by default. This improves disk throughput (from 320MiB/sec to 600MiB/sec in `dd` on a 2015 MacBook Pro) and disk space handling.
|
||||
Existing disks are kept in qcow format, if you want to switch to raw format you need to "Remove all data" or "Reset to factory defaults". See [Disk utilization](../space.md)
|
||||
Existing disks are kept in qcow format, if you want to switch to raw format you need to "Remove all data" or "Reset to factory defaults". See [Disk utilization](../mac/space.md)
|
||||
- DNS name `docker.for.mac.host.internal` should be used instead of `docker.for.mac.localhost` (still valid) for host resolution from containers, since since there is an RFC banning the use of subdomains of localhost. See https://tools.ietf.org/html/draft-west-let-localhost-be-localhost-06.
|
||||
|
||||
* Bug fixes and minor changes
|
||||
|
|
@ -4,6 +4,8 @@ keywords: Docker Desktop for Windows, release notes
|
|||
title: Release notes for previous versions
|
||||
toc_min: 1
|
||||
toc_max: 2
|
||||
redirect_from:
|
||||
- /desktop/windows/release-notes/archive/
|
||||
---
|
||||
|
||||
This page contains release notes for older versions of Docker Desktop for Windows.
|
||||
|
|
@ -62,7 +64,7 @@ This page contains release notes for older versions of Docker Desktop for Window
|
|||
- Linux Kernel 4.9.93 with CEPH, DRBD, RBD, MPLS_ROUTING and MPLS_IPTUNNEL enabled
|
||||
|
||||
* New
|
||||
- Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker for Windows settings and use kubectl commands as well as Docker commands. See [the Kubernetes section](../../kubernetes.md)
|
||||
- Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker for Windows settings and use kubectl commands as well as Docker commands. See [the Kubernetes section](../kubernetes.md)
|
||||
|
||||
* Bug fixes and minor changes
|
||||
- AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset the disk image (in Settings > Reset menu) before updating to the next major update. You can check documentation to [save images](https://docs.docker.com/engine/reference/commandline/save/#examples) and [backup volumes](https://docs.docker.com/storage/volumes/#backup-restore-or-migrate-data-volumes)
|
||||
|
|
@ -141,7 +143,7 @@ This page contains release notes for older versions of Docker Desktop for Window
|
|||
- Fix Linuxkit start on Windows RS4 Insider. Fixes [docker/for-win#1458](https://github.com/docker/for-win/issues/1458), [docker/for-win#1514](https://github.com/docker/for-win/issues/1514), [docker/for-win#1640](https://github.com/docker/for-win/issues/1640)
|
||||
- Fix risk of privilege escalation. (https://www.tenable.com/sc-report-templates/microsoft-windows-unquoted-service-path-vulnerability)
|
||||
- All users present in the docker-users group are now able to use Docker. Fixes [docker/for-win#1732](https://github.com/docker/for-win/issues/1732)
|
||||
- Migration of Docker Toolbox images is not proposed in Docker For Windows installer (still possible to [migrate Toolbox images manually](../../../toolbox/index.md) ).
|
||||
- Migration of Docker Toolbox images is not proposed in Docker For Windows installer (still possible to migrate Toolbox images manually).
|
||||
- Better cleanup for Windows containers and images on reset/uninstall. Fixes [docker/for-win#1580](https://github.com/docker/for-win/issues/1580), [docker/for-win#1544](https://github.com/docker/for-win/issues/1544), [docker/for-win#191](https://github.com/docker/for-win/issues/191)
|
||||
- Desktop icon creation is optional in installer; do not recreate Desktop icon on upgrade (effective on next upgrade). Fixes [docker/for-win#246](https://github.com/docker/for-win/issues/246), [docker/for-win#925](https://github.com/docker/for-win/issues/925), [docker/for-win#1551](https://github.com/docker/for-win/issues/1551)
|
||||
|
||||
|
|
@ -4,12 +4,14 @@ keywords: Docker Desktop for Mac, edge, release notes
|
|||
title: Docker Desktop for Mac Edge release notes
|
||||
toc_min: 1
|
||||
toc_max: 2
|
||||
redirect_from:
|
||||
- /desktop/mac/release-notes/edge-releases/
|
||||
---
|
||||
|
||||
This page contains information about Docker Desktop Edge releases. Edge releases give you early access to our newest features. Note that some of the features may be experimental, and some of them may not ever reach the Stable release.
|
||||
|
||||
For information about Stable releases, see the [Stable release notes](index.md). For Docker Desktop system requirements, see
|
||||
[What to know before you install](../install.md#system-requirements).
|
||||
For information about Stable releases, see the [Stable release notes](../mac/index.md). For Docker Desktop system requirements, see
|
||||
[What to know before you install](../mac/install.md#system-requirements).
|
||||
|
||||
## Docker Desktop Community 2.5.4
|
||||
2020-12-07
|
||||
|
|
@ -1209,7 +1211,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
- [Docker 17.12.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.12.0-ce)
|
||||
|
||||
* New
|
||||
- Experimental Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker For Mac Preferences and use kubectl commands as well as docker commands. See [the Kubernetes section](../../kubernetes.md)
|
||||
- Experimental Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker For Mac Preferences and use kubectl commands as well as docker commands. See [the Kubernetes section](../kubernetes.md)
|
||||
- DNS name `docker.for.mac.host.internal` should be used instead of `docker.for.mac.localhost` (still valid) for host resolution from containers, since since there is an RFC banning the use of subdomains of localhost (See https://tools.ietf.org/html/draft-west-let-localhost-be-localhost-06).
|
||||
|
||||
* Bug fixes and minor changes
|
||||
|
|
@ -1432,7 +1434,7 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
- Add daemon options validation
|
||||
- Diagnose can be cancelled & Improved help information. Fixes [docker/for-mac#1134](https://github.com/docker/for-mac/issues/1134), [docker/for-mac#1474](https://github.com/docker/for-mac/issues/1474)
|
||||
- Support paging of Docker Cloud [repositories](../../../docker-hub/repos.md) and [organizations](../../../docker-hub/orgs.md). Fixes [docker/for-mac#1538](https://github.com/docker/for-mac/issues/1538)
|
||||
- Support paging of Docker Cloud [repositories](../../docker-hub/repos.md) and [organizations](../../docker-hub/orgs.md). Fixes [docker/for-mac#1538](https://github.com/docker/for-mac/issues/1538)
|
||||
|
||||
### Docker Community Edition 17.06.1-ce-mac20, 2017-07-18
|
||||
|
||||
|
|
@ -1681,7 +1683,7 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
**New**
|
||||
|
||||
- More options when moving disk image (see [Storage location](../space.md) under Advanced preference settings)
|
||||
- More options when moving disk image (see [Storage location](../mac/space.md) under Advanced preference settings)
|
||||
- Filesharing and daemon table empty fields are editable
|
||||
- DNS forwarder ignores responses from malfunctioning servers ([docker/for-mac#1025](https://github.com/docker/for-mac/issues/1025))
|
||||
- DNS forwarder send all queries in parallel, process results in order
|
||||
|
|
@ -1866,9 +1868,9 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
**New**
|
||||
|
||||
- Dedicated preference pane for advanced configuration of the docker daemon (edit daemon.json). See [Daemon Advanced (JSON configuration file)](../index.md#docker-engine).
|
||||
- Dedicated preference pane for advanced configuration of the docker daemon (edit daemon.json). See [Daemon Advanced (JSON configuration file)](../mac/index.md#docker-engine).
|
||||
|
||||
- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](../index.md#docker-engine).
|
||||
- Docker Experimental mode can be toggled. See [Daemon Basic (experimental mode and registries)](../mac/index.md#docker-engine).
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
@ -2024,7 +2026,7 @@ issue is being investigated. The workaround is to restart Docker.app.
|
|||
traversals of large directories are currently slow. Additionally, containers
|
||||
that perform large numbers of directory operations, such as repeated scans of
|
||||
large directory trees, may suffer from poor performance. More information is
|
||||
available in [Known Issues](../troubleshoot.md#known-issues) in Troubleshooting.
|
||||
available in [Known Issues](../mac/troubleshoot.md#known-issues) in Troubleshooting.
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart `Docker.app`.
|
||||
|
||||
|
|
@ -2054,7 +2056,7 @@ with `osxfs`. In particular, writes of small blocks and traversals of large
|
|||
directories are currently slow. Additionally, containers that perform large
|
||||
numbers of directory operations, such as repeated scans of large directory
|
||||
trees, may suffer from poor performance. More information is available in
|
||||
[Known Issues](../troubleshoot.md#known-issues) in Troubleshooting.
|
||||
[Known Issues](../mac/troubleshoot.md#known-issues) in Troubleshooting.
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart Docker.app.
|
||||
|
||||
|
|
@ -2088,7 +2090,7 @@ trees, may suffer from poor performance. More information is available in
|
|||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large
|
||||
directories are currently slow. Additionally, containers that perform large
|
||||
numbers of directory operations, such as repeated scans of large directory
|
||||
trees, may suffer from poor performance. For more information and workarounds, see the bullet on performance of bind-mounted directories in [Known Issues](../troubleshoot.md#known-issues) in Troubleshooting.
|
||||
trees, may suffer from poor performance. For more information and workarounds, see the bullet on performance of bind-mounted directories in [Known Issues](../mac/troubleshoot.md#known-issues) in Troubleshooting.
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart `Docker.app`.
|
||||
|
||||
|
|
@ -2114,7 +2116,7 @@ trees, may suffer from poor performance. For more information and workarounds, s
|
|||
|
||||
* Docker.app sometimes uses 200% CPU after macOS wakes up from sleep mode. The issue is being investigated. The workaround is to restart Docker.app
|
||||
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. For more information and workarounds, see the bullet on performance of bind-mounted directories in [Known Issues](../troubleshoot.md#known-issues) in Troubleshooting.
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. For more information and workarounds, see the bullet on performance of bind-mounted directories in [Known Issues](../mac/troubleshoot.md#known-issues) in Troubleshooting.
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart Docker.app
|
||||
|
||||
|
|
@ -2137,7 +2139,7 @@ trees, may suffer from poor performance. For more information and workarounds, s
|
|||
|
||||
* Docker.app sometimes uses 200% CPU after macOS wakes up from sleep mode. The issue is being investigated. The workaround is to restart Docker.app
|
||||
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. More information is available in [Known Issues](../troubleshoot.md#known-issues) in [Troubleshooting](../troubleshoot.md)
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. More information is available in [Known Issues](../mac/troubleshoot.md#known-issues) in [Troubleshooting](../mac/troubleshoot.md)
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart Docker.app
|
||||
|
||||
|
|
@ -2161,7 +2163,7 @@ events or unexpected unmounts.
|
|||
|
||||
**New**
|
||||
|
||||
* Docker for Mac is now available from 2 channels: **stable** and **beta**. New features and bug fixes will go out first in auto-updates to users in the beta channel. Updates to the stable channel are much less frequent and happen in sync with major and minor releases of the Docker engine. Only features that are well-tested and ready for production are added to the stable channel releases. For downloads of both and more information, see the [installation guide](../install.md).
|
||||
* Docker for Mac is now available from 2 channels: **stable** and **beta**. New features and bug fixes will go out first in auto-updates to users in the beta channel. Updates to the stable channel are much less frequent and happen in sync with major and minor releases of the Docker engine. Only features that are well-tested and ready for production are added to the stable channel releases. For downloads of both and more information, see the [installation guide](../mac/install.md).
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
@ -2184,7 +2186,7 @@ events or unexpected unmounts.
|
|||
|
||||
* Docker.app sometimes uses 200% CPU after macOS wakes up from sleep mode. The issue is being investigated. The workaround is to restart Docker.app
|
||||
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks, and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. For more information and workarounds, see [Known Issues](../troubleshoot.md#known-issues) in [Logs and Troubleshooting](../troubleshoot.md).
|
||||
* There are a number of issues with the performance of directories bind-mounted with `osxfs`. In particular, writes of small blocks, and traversals of large directories are currently slow. Additionally, containers that perform large numbers of directory operations, such as repeated scans of large directory trees, may suffer from poor performance. For more information and workarounds, see [Known Issues](../mac/troubleshoot.md#known-issues) in [Logs and Troubleshooting](../mac/troubleshoot.md).
|
||||
|
||||
* Under some unhandled error conditions, `inotify` event delivery can fail and become permanently disabled. The workaround is to restart Docker.app
|
||||
|
||||
|
|
@ -2228,7 +2230,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot.md#known-issues) in [Troubleshooting](../troubleshoot.md)
|
||||
* See [Known Issues](../mac/troubleshoot.md#known-issues) in [Troubleshooting](../mac/troubleshoot.md)
|
||||
|
||||
### Beta 18.1 Release Notes (2016-07-07 1.12.0-rc3-beta18.1)
|
||||
|
||||
|
|
@ -2254,7 +2256,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot.md#known-issues) in [Troubleshooting](../troubleshoot.md)
|
||||
* See [Known Issues](../mac/troubleshoot.md#known-issues) in [Troubleshooting](../mac/troubleshoot.md)
|
||||
|
||||
### Beta 18 Release Notes (2016-07-06 1.12.0-rc3-beta18)
|
||||
|
||||
|
|
@ -2275,7 +2277,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot.md#known-issues) in [Troubleshooting](../troubleshoot.md)
|
||||
* See [Known Issues](../mac/troubleshoot.md#known-issues) in [Troubleshooting](../mac/troubleshoot.md)
|
||||
|
||||
### Beta 17 Release Notes (2016-06-29 1.12.0-rc2-beta17)
|
||||
|
||||
|
|
@ -2285,7 +2287,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Bug fixes and minor changes**
|
||||
|
||||
* Documentation moved to [https://docs.docker.com/desktop/mac/](../index.md)
|
||||
* Documentation moved to [https://docs.docker.com/desktop/mac/](../mac/index.md)
|
||||
* Allow non-admin users to launch the app for the first time (using admin creds)
|
||||
* Prompt non-admin users for admin password when needed in Preferences
|
||||
* Fixed download links, documentation links
|
||||
|
|
@ -2294,7 +2296,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot.md#known-issues) in [Troubleshooting](../troubleshoot.md)
|
||||
* See [Known Issues](../mac/troubleshoot.md#known-issues) in [Troubleshooting](../mac/troubleshoot.md)
|
||||
|
||||
### Beta 16 Release Notes (2016-06-17 1.12.0-rc2-beta16)
|
||||
|
||||
|
|
@ -2316,7 +2318,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot.md#known-issues) in [Troubleshooting](../troubleshoot.md)
|
||||
* See [Known Issues](../mac/troubleshoot.md#known-issues) in [Troubleshooting](../mac/troubleshoot.md)
|
||||
|
||||
### Beta 15 Release Notes (2016-06-10 1.11.2-beta15)
|
||||
|
||||
|
|
@ -2340,7 +2342,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* See [Known Issues](../troubleshoot.md#known-issues) in [Troubleshooting](../troubleshoot.md)
|
||||
* See [Known Issues](../mac/troubleshoot.md#known-issues) in [Troubleshooting](../mac/troubleshoot.md)
|
||||
|
||||
### Beta 14 Release Notes (2016-06-02 1.11.1-beta14)
|
||||
|
||||
|
|
@ -4,12 +4,14 @@ keywords: Docker Desktop for Windows, edge, release notes
|
|||
title: Docker Desktop for Windows Edge Release notes
|
||||
toc_min: 1
|
||||
toc_max: 2
|
||||
redirect_from:
|
||||
- /desktop/windows/release-notes/edge-releases/
|
||||
---
|
||||
|
||||
This page contains information about Docker Desktop Edge releases. Edge releases give you early access to our newest features. Note that some of the features may be experimental, and some of them may not ever reach the Stable release.
|
||||
|
||||
For information about Stable releases, see the [Stable release notes](index.md). For Docker Desktop system requirements, see
|
||||
[What to know before you install](../install.md#system-requirements).
|
||||
For information about Stable releases, see the [Stable release notes](../windows/release-notes/index.md). For Docker Desktop system requirements, see
|
||||
[What to know before you install](../windows/install.md#system-requirements).
|
||||
|
||||
## Docker Desktop Community 2.5.4
|
||||
2020-12-07
|
||||
|
|
@ -96,7 +98,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
|
||||
### New
|
||||
|
||||
- If you have enabled [Vulnerability Scanning](../../../docker-hub/vulnerability-scanning.md) in Docker Hub, the scan results will now appear in Docker Desktop.
|
||||
- If you have enabled [Vulnerability Scanning](../../docker-hub/vulnerability-scanning.md) in Docker Hub, the scan results will now appear in Docker Desktop.
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -208,7 +210,7 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for
|
|||
|
||||
### New
|
||||
|
||||
- In partnership with Snyk, Docker Desktop launches [vulnerability scanning](https://docs.docker.com/engine/scan/) for Docker local images.
|
||||
- In partnership with Snyk, Docker Desktop launches [vulnerability scanning](../../engine/scan/index.md) for Docker local images.
|
||||
- Docker ECS plugin has been replaced by [ECS cloud integration](https://docs.docker.com/engine/context/ecs-integration/)
|
||||
- Docker UI:
|
||||
- The Images view now has search and filter options.
|
||||
|
|
@ -578,7 +580,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
### Bug fixes and minor changes
|
||||
|
||||
- Added a prerequisite check in the installer for the `LanmanServer` service. Fixes [docker/for-win#5150](https://github.com/docker/for-win/issues/5150).
|
||||
- DockerNAT has been removed from Docker Desktop 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](../networking.md#use-cases-and-workarounds).
|
||||
- DockerNAT has been removed from Docker Desktop 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](../windows/networking.md#use-cases-and-workarounds).
|
||||
- Ceph support has been removed from Docker Desktop to save disk space.
|
||||
- Fixed an issue that caused the Windows log file archive to grow indefinitely. Fixes [docker/for-win#5113](https://github.com/docker/for-win/issues/5113).
|
||||
|
||||
|
|
@ -618,7 +620,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
|
||||
### 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](../networking.md#use-cases-and-workarounds).
|
||||
- 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](../windows/networking.md#use-cases-and-workarounds).
|
||||
|
||||
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.
|
||||
|
|
@ -740,7 +742,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
|
||||
To access the Dashboard UI, select the Docker menu from the system tray and then click **Dashboard**.
|
||||
|
||||
- **WSL 2 backend:** The new Docker Desktop WSL 2 backend replaces the Docker Desktop WSL 2 Tech Preview. The 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](../wsl.md).
|
||||
- **WSL 2 backend:** The new Docker Desktop WSL 2 backend replaces the Docker Desktop WSL 2 Tech Preview. The 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](../windows/wsl.md).
|
||||
|
||||
- **New file sharing implementation:** Docker Desktop introduces a new file sharing implementation which uses gRPC, FUSE, and Hypervisor sockets instead of Samba, CIFS, and Hyper-V networking. The new implementation offers improved I/O performance. Additionally, when using the new file system:
|
||||
|
||||
|
|
@ -831,7 +833,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
|
||||
#### New
|
||||
|
||||
- [Docker Desktop WSL 2 Tech Preview](../wsl.md)
|
||||
- [Docker Desktop WSL 2 Tech Preview](../windows/wsl.md)
|
||||
|
||||
#### Bug fixes and minor changes
|
||||
|
||||
|
|
@ -1360,7 +1362,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
- [Docker 18.02.0-ce-rc1](https://github.com/docker/docker-ce/releases/tag/v18.02.0-ce-rc1)
|
||||
|
||||
* New
|
||||
- Experimental Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker for Windows settings and use kubectl commands as well as docker commands. See [the Kubernetes section](../../kubernetes.md).
|
||||
- Experimental Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker for Windows settings and use kubectl commands as well as docker commands. See [the Kubernetes section](../kubernetes.md).
|
||||
- LCOW containers can now be run next to Windows containers (on Windows RS3 build 16299 and later). Use `--platform=linux` in Windows container mode to run Linux Containers On Windows. Note that LCOW is still experimental, and requires daemon `experimental` option.
|
||||
|
||||
* Bug fixes and minor changes
|
||||
|
|
@ -2007,7 +2009,7 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
|
|||
**New**
|
||||
|
||||
- Windows containers settings panel and options are working. In previous releases, settings were not implemented for
|
||||
[Windows containers mode](../index.md#switch-between-windows-and-linux-containers).
|
||||
[Windows containers mode](../windows/index.md#switch-between-windows-and-linux-containers).
|
||||
- Windows containers: Restart from the settings panel works
|
||||
- Windows containers: Factory default
|
||||
- Windows containers: `Daemon.json` can be modified
|
||||
|
|
@ -2331,7 +2333,7 @@ work. Some insider builds may not work.
|
|||
**Known issues**
|
||||
|
||||
* Only UTF-8 passwords are supported for host filesystem sharing
|
||||
* Docker automatically disables lingering net adapters. The only way to remove them is manually using `devmgmt.msc` as documented in [Troubleshooting](../troubleshoot.md#networking-issues).
|
||||
* Docker automatically disables lingering net adapters. The only way to remove them is manually using `devmgmt.msc` as documented in [Troubleshooting](../windows/troubleshoot.md#networking-issues).
|
||||
|
||||
### Beta 22 Release (2016-08-11 1.12.0-beta22)
|
||||
|
||||
|
|
@ -2339,13 +2341,13 @@ Unreleased. See Beta 23 for changes.
|
|||
|
||||
**Known issues**
|
||||
|
||||
* Docker automatically disables lingering net adapters. The only way to remove them is manually using `devmgmt.msc` as documented in [Troubleshooting](../troubleshoot.md#networking-issues).
|
||||
* Docker automatically disables lingering net adapters. The only way to remove them is manually using `devmgmt.msc` as documented in [Troubleshooting](../windows/troubleshoot.md#networking-issues).
|
||||
|
||||
### Beta 21 Release (2016-07-28 1.12.0-beta21)
|
||||
|
||||
**New**
|
||||
|
||||
* Docker for Windows is now available from two channels: **stable** and **beta**. New features and bug fixes go out first in auto-updates to users in the beta channel. Updates to the stable channel are much less frequent and happen in sync with major and minor releases of the Docker engine. Only features that are well-tested and ready for production are added to the stable channel releases. For downloads of both and more information, see [Install Docker Desktop on Windows](../install.md).
|
||||
* Docker for Windows is now available from two channels: **stable** and **beta**. New features and bug fixes go out first in auto-updates to users in the beta channel. Updates to the stable channel are much less frequent and happen in sync with major and minor releases of the Docker engine. Only features that are well-tested and ready for production are added to the stable channel releases. For downloads of both and more information, see [Install Docker Desktop on Windows](../windows/install.md).
|
||||
|
||||
* Removed the docker host name. Containers with exported ports are reachable via localhost.
|
||||
|
||||
|
|
@ -2614,7 +2616,7 @@ This Beta release includes some significant changes:
|
|||
* The GUI now runs in non-elevated mode and connects to an elevated Windows service
|
||||
* Allocate virtual machine memory by 256 MB increments, instead of 1 GB
|
||||
* Show a meaningful error when the user has an empty password
|
||||
* Improved [Troubleshooting](../troubleshoot.md) page
|
||||
* Improved [Troubleshooting](../windows/troubleshoot.md) page
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
@ -2638,7 +2640,7 @@ This Beta release includes some significant changes:
|
|||
|
||||
**Known issues**
|
||||
|
||||
* Due to limitation in the Windows NAT implementation, co-existence with other NAT prefixes needs to be carefully managed. See [Troubleshooting](../troubleshoot.md) for more details.
|
||||
* Due to limitation in the Windows NAT implementation, co-existence with other NAT prefixes needs to be carefully managed. See [Troubleshooting](../windows/troubleshoot.md) for more details.
|
||||
|
||||
* Logs for the windows service are not aggregated with logs from the GUI. This is expected to be fixed in future versions.
|
||||
|
||||
|
|
@ -2666,7 +2668,7 @@ This Beta release includes some significant changes:
|
|||
|
||||
**Known issues**
|
||||
|
||||
* Due to limitation in the Windows NAT implementation, co-existence with other NAT prefixes needs to be carefully managed. See [Troubleshooting](../troubleshoot.md) for more details.
|
||||
* Due to limitation in the Windows NAT implementation, co-existence with other NAT prefixes needs to be carefully managed. See [Troubleshooting](../windows/troubleshoot.md) for more details.
|
||||
|
||||
|
||||
### Beta 9 Release (2016-04-26 1.11.0-beta9)
|
||||
Loading…
Reference in New Issue