mirror of https://github.com/docker/docs.git
Merge branch 'combine-eng-relnotes-737' of github.com:docker/docs-private into combine-eng-relnotes-737
This commit is contained in:
commit
61df683f6f
|
@ -22,14 +22,13 @@ consistency and compatibility reasons.
|
||||||
|
|
||||||
### New features for Docker Engine EE and CE
|
### New features for Docker Engine EE and CE
|
||||||
|
|
||||||
* Docker CE-EE node activate, which enables a user to apply a license to a CE binary and have it seamlessly upgrade
|
* [Docker Build architecture overhaul](/develop/develop-images/build_enhancements), which integrates buildKit to provide enhancements to `docker build`
|
||||||
to the EE binary
|
|
||||||
* Docker Build architecture overhaul, which integrates buildKit to provide enhancements to `docker build`
|
|
||||||
* Integrated containerd runtime to serve as a foundation for Docker Engine
|
* Integrated containerd runtime to serve as a foundation for Docker Engine
|
||||||
|
* [Docker CE-EE node activate](/engine/ce-ee-node-activate), which enables a user to apply a license to a CE binary and have it seamlessly upgrade to the EE binary
|
||||||
|
|
||||||
### New features for Docker Engine EE
|
### New features for Docker Engine EE
|
||||||
* Improved FIPS implementation to include Windows support.
|
* [FIPS Compliance added for Windows Server 2016 and later](/install/windows/docker-ee)
|
||||||
* Docker Content Trust Enforcement for the Enterprise Engine. This prevents Docker Engine from running containers not signed by a specific organization.
|
* [Docker Content Trust Enforcement](/engine/security/trust/content_trust) for the Enterprise Engine. This allows Docker Engine from running containers not signed by a specific organization.
|
||||||
|
|
||||||
### Bug fixes
|
### Bug fixes
|
||||||
|
|
||||||
|
@ -37,12 +36,14 @@ to the EE binary
|
||||||
|
|
||||||
### Depreciation Notice
|
### Depreciation Notice
|
||||||
|
|
||||||
Docker EE 2.1 Platform release, will serve to deprecate support of Device Mapper in a future release. It will continue to be supported at this time, but
|
Docker EE 2.1 Platform release, will serve to deprecate support of Device Mapper in a future release.
|
||||||
support will be removed in a future release. Docker will continue to support Device Mapper for for existing EE 2.0 and 2.1 customers.
|
It will continue to be supported at this time, but support will be removed in a future release. Docker
|
||||||
Please contact Sales for more information.
|
will continue to support Device Mapper for for existing EE 2.0 and 2.1 customers. Please [contact Sales](https://www.docker.com/company/contact-sales) for more information.
|
||||||
|
|
||||||
Docker reocmmends that existing customers migrate to using Overlay2 for the storage driver. The Overlay2 storage driver is now the default
|
Docker recommends that existing customers [migrate to using Overlay2 for the storage driver]
|
||||||
for Docker engine implementations.
|
(https://success.docker.com/article/how-do-i-migrate-an-existing-ucp-cluster-to-the-overlay2-graph-driver).
|
||||||
|
The [Overlay2 storage driver](https://docs.docker.com/storage/storagedriver/overlayfs-driver/) is now the
|
||||||
|
default for Docker engine implementations.
|
||||||
|
|
||||||
## Older Docker Engine EE Release notes
|
## Older Docker Engine EE Release notes
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue