diff --git a/engine/breaking_changes.md b/engine/breaking_changes.md index 7e8fdd7fae..e24f4194c7 100644 --- a/engine/breaking_changes.md +++ b/engine/breaking_changes.md @@ -8,29 +8,29 @@ keywords: title: Breaking changes and incompatibilities --- -Every Engine release strives to be backward compatible with its predecessors. -In all cases, the policy is that feature removal is communicated two releases +Every Engine release strives to be backward compatible with its predecessors, +and interface stability is always a priority at Docker. + +In all cases, feature removal is communicated three releases in advance and documented as part of the [deprecated features](deprecated.md) page. + +The following list compiles any updates to Docker Engine that created +backwards-incompatibility for old versions of Docker tools. -Unfortunately, Docker is a fast moving project, and newly introduced features -may sometime introduce breaking changes and/or incompatibilities. This page -documents these by Engine version. - -# Engine 1.12 - -Docker clients <= 1.9.2 used an invalid Host header when making request to the -daemon. Docker 1.12 is built using golang 1.6 which is now checking the validity -of the Host header and as such clients <= 1.9.2 can't talk anymore to the daemon. -[An environment variable was added to overcome this issue.](reference/commandline/dockerd.md#miscellaneous-options) +> Note: In the case of your local environment, you should be updating your + Docker Engine using [Docker for Mac](/docker-for-mac), + [Docker for Windows](/docker-for-windows). That way all your tools stay + in sync with Docker Engine. # Engine 1.10 -There were two breaking changes in the 1.10 release. +There were two breaking changes in the 1.10 release that affected +Registry and Docker Content Trust: -## Registry +**Registry** -Registry 2.3 includes improvements to the image manifest that have caused a +Registry 2.3 includes improvements to the image manifest that caused a breaking change. Images pushed by Engine 1.10 to a Registry 2.3 cannot be pulled by digest by older Engine versions. A `docker pull` that encounters this situation returns the following error: @@ -47,7 +47,7 @@ If you are using an older Registry version (< 2.3), this problem does not occur with any version of the Engine CLI; push, pull, with and without content trust work as you would expect. -## Docker Content Trust +**Docker Content Trust** Engine older than the current 1.10 cannot pull images from repositories that have enabled key delegation. Key delegation is a feature which requires a