This issue will be used as a synchronization point between docker/distribution PRs and core Docker changes required to implement the multi-architecture support between registry schema changes (to enable tagging with information like arch and os) and smart parsing of fat manifests on the daemon side during pull.

Also, a design for fat manifest creation (which may need to be different than basic docker push) will be discussed here, and, as needed, PRs will be created to implement these capabilities.

References

• doc/spec: generic distribution content manifests distribution/distribution#62 - proposal for new generic content schema for registry v2; rework by @stevvooe TBD
• architecture and operating system support distribution/distribution#200 - specific issue to collect multi-arch requirements/discussion on docker/distribution repo

Completed work

• Move manifest package to schema1 distribution/distribution#912 - moves current schema to specific versioned package to make schema2 implementation work possible