github.com/sijibomii/docker@v0.0.0-20231230191044-5cf6ca554647/docs/breaking_changes.md (about) 1 <!--[metadata]> 2 +++ 3 aliases = ["/engine/misc/breaking/"] 4 title = "Breaking changes" 5 description = "Breaking changes" 6 keywords = ["docker, documentation, about, technology, breaking", 7 "incompatibilities"] 8 [menu.main] 9 parent = "engine_use" 10 weight=80 11 +++ 12 <![end-metadata]--> 13 14 # Breaking changes and incompatibilities 15 16 Every Engine release strives to be backward compatible with its predecessors. 17 In all cases, the policy is that feature removal is communicated two releases 18 in advance and documented as part of the [deprecated features](deprecated.md) 19 page. 20 21 Unfortunately, Docker is a fast moving project, and newly introduced features 22 may sometime introduce breaking changes and/or incompatibilities. This page 23 documents these by Engine version. 24 25 # Engine 1.10 26 27 There were two breaking changes in the 1.10 release. 28 29 ## Registry 30 31 Registry 2.3 includes improvements to the image manifest that have caused a 32 breaking change. Images pushed by Engine 1.10 to a Registry 2.3 cannot be 33 pulled by digest by older Engine versions. A `docker pull` that encounters this 34 situation returns the following error: 35 36 ``` 37 Error response from daemon: unsupported schema version 2 for tag TAGNAME 38 ``` 39 40 Docker Content Trust heavily relies on pull by digest. As a result, images 41 pushed from the Engine 1.10 CLI to a 2.3 Registry cannot be pulled by older 42 Engine CLIs (< 1.10) with Docker Content Trust enabled. 43 44 If you are using an older Registry version (< 2.3), this problem does not occur 45 with any version of the Engine CLI; push, pull, with and without content trust 46 work as you would expect. 47 48 ## Docker Content Trust 49 50 Engine older than the current 1.10 cannot pull images from repositories that 51 have enabled key delegation. Key delegation is a feature which requires a 52 manual action to enable.