[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-11。"],[[["\u003cp\u003eContainer Registry supports Docker Image Manifest V2 (both Schema 1 and Schema 2) and Open Container Initiative (OCI) image formats for container images.\u003c/p\u003e\n"],["\u003cp\u003eDocker V2 images, which supersede the deprecated Docker V1 images, offer content-addressable images and multi-architecture support.\u003c/p\u003e\n"],["\u003cp\u003eManifest lists (for Docker V2) and image indexes (for OCI) allow a single tag or digest to represent multiple versions or platforms of an image.\u003c/p\u003e\n"],["\u003cp\u003eThe Docker V1 image format is deprecated and cannot be used with Container Registry, and all users must use Docker V2 or OCI compatible images.\u003c/p\u003e\n"],["\u003cp\u003eUpgrading from Docker V1 to Docker V2 images can be done by pulling existing V1 images with \u003ccode\u003edocker pull\u003c/code\u003e and then pushing them with \u003ccode\u003edocker push\u003c/code\u003e, if using a docker version higher than 1.6.\u003c/p\u003e\n"]]],[],null,["# Container image formats\n\nContainer Registry supports the following container image formats:\n\n- [Docker Image Manifest V2, Schema 1](https://docs.docker.com/registry/spec/manifest-v2-1/)\n- [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)\n- [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec)\n\nDocker V2\n---------\n\n[Docker V2 image manifest](https://docs.docker.com/registry/spec/manifest-v2-2/)\nis a specification for container images that allows\nmulti-architecture images and supports content-addressable images.\n\nDocker V2 images supersede Docker V1 images, which are\n[deprecated](/container-registry/docs/support/deprecation-notices#docker_registry_v1_api_and_docker_clients_below_version_16).\n\nManifest lists\n--------------\n\n[Manifest lists](https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list)\nare part of the Docker V2, Schema 2 and OCI images.\n\nManifest lists allow a single digest or tag to represent multiple forms of an\nimage.\n\nOCI format\n----------\n\nThe OCI format is a specification for container images based on the\nDocker Image Manifest Version 2, Schema 2 format. Container Registry\nsupports pushing and pulling OCI images.\n\nImage indexes\n-------------\n\n[Image indexes](https://github.com/opencontainers/image-spec/blob/28462ef6944123de00cf27e812309cbf5d82da71/image-index.md)\nare the equivalent of manifest lists in OCI images.\n\nLike manifest lists, an image index manifest refers to multiple image\nmanifests. Image indexes are useful for multi-platform images.\n\nDeprecation of Docker V1 image format\n-------------------------------------\n\nAs of February 28, 2017, the [Docker V2 registry\nspecification](https://docs.docker.com/registry/spec/api/)\nreplaced the Docker V1 specification. The Docker V1 specification is deprecated,\nand Docker V1 images cannot be used with Container Registry.\n\nDocker V2 made a set of changes to the Docker image format to allow for\ncontent-addressable images and to remove complexity in tracking image layers.\nDocker V2 image manifests contain all the content addresses (\"digests\") of the\nimage's layers, whereas Docker V1 images did not.\n\nFor more information, refer to\n[Deprecation Notices](/container-registry/docs/support/deprecation-notices).\n\n### Upgrading Docker V1 images to Docker V2 images\n\nTo upgrade your V1 images to V2 images, ensure that Docker v1.6 or higher is\ninstalled. Then, run the following commands to pull and then re-push the\nimages to Container Registry: \n\n docker pull gcr.io/[your-project-id]/[image]:[tag]\n docker push gcr.io/[your-project-id]/[image]:[tag]"]]