Stay organized with collections
Save and categorize content based on your preferences.
Artifact Registry stores the following artifact formats.
Formats
Docker
Store Docker container images and Helm charts packaged in OCI format.
For more information on container image formats, see
Container images.
Maven
Store Java packages that you build with Maven or Gradle. For more
information on storing Java packages in Artifact Registry, see
Manage Java packages.
npm
Store Node.js packages that you manage with npm. For more information
on storing Node.js packages in Artifact Registry, see
Manage Node.js packages
Python
Store Python packages. For more information on storing Python packages
in Artifact Registry, see
Manage Python packages
Apt
Store Debian packages that you manage with Apt. For more information on
storing Debian packages in Artifact Registry, see
Manage Debian packages.
Yum
Store RPM packages that you manage with Yum and DNF. For more
information on storing RPM packages, see
Manage RPM packages.
Kubeflow
Store Kubeflow pipeline templates. A pipeline template
lets you reuse ML workflow definitions when you're managing ML workflows in
Vertex AI.
Vertex AI is the Google Cloud ML platform for building,
deploying, and managing ML models. To learn about creating pipeline templates
and using them with Artifact Registry, see
Create, upload, and use a pipeline template.
Go
Store Go modules. For more information on storing Go modules in
Artifact Registry, see
Work with Go modules.
Generic
Store generic artifacts. Generic artifacts are versioned, immutable
artifacts that don't adhere to any specific package format. For more
information on storing generic artifacts in Artifact Registry, see
Work with other artifact formats.
Container images
Artifact Registry supports the following container image formats:
Docker V2 image manifest
is a specification for container images that allows
multi-architecture images and supports content-addressable images.
Docker V2 images supersede Docker V1 images, which are
deprecated.
OCI Image Format
The OCI image format is a specification for container images based on the
Docker Image Manifest Version 2, Schema 2 format. Artifact Registry implements the
OCI Specification, an API protocol to help
standardize distribution of content.
You can store artifacts that support the OCI image format in
Artifact Registry Docker repositories. For example:
Helm 3 charts
can be packaged in OCI format. For more information, see the
Artifact Registry Helm overview.
Authentication is similar to authentication for
Docker clients.
Singularity can read settings that the credential helper added to the
Docker client config.json. If you are using a token or service account
key for password authentication, you can use the
singularity remote login command to
log in with your credentials.
Use the singularity pull command with the
oras:// URI to pull images.
Use the singularity push command with the
oras:// URI to push images.
For example, the following command pulls my-app:latest from the repository
us-west1.pkg.dev/my-project/sif-repo.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eArtifact Registry supports a variety of artifact formats, including Docker, Maven, npm, Python, Apt, Yum, Kubeflow, Go, and generic artifacts.\u003c/p\u003e\n"],["\u003cp\u003eDocker container images and Helm charts packaged in OCI format can be stored, and Artifact Registry supports Docker Image Manifest V2, Schema 1 and 2, and Open Container Initiative (OCI) Image Format Specifications.\u003c/p\u003e\n"],["\u003cp\u003eThe platform is compatible with Docker V2 images, which supersede the deprecated Docker V1 images, and supports multi-architecture images and content-addressable images.\u003c/p\u003e\n"],["\u003cp\u003eManifest lists in Docker V2 and image indexes in OCI images enable a single tag or digest to represent multiple image forms, especially useful for multi-platform images.\u003c/p\u003e\n"],["\u003cp\u003eSingularity can pull and push Docker and OCI images from and to private registries, using commands like \u003ccode\u003esingularity pull\u003c/code\u003e and \u003ccode\u003esingularity push\u003c/code\u003e with \u003ccode\u003eoras://\u003c/code\u003e URI, and it is compatible with Artifact Registry authentication methods.\u003c/p\u003e\n"]]],[],null,["# Supported formats\n\nArtifact Registry stores the following artifact formats.\n\nContainer images\n----------------\n\nArtifact 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) Image Format Specifications](https://github.com/opencontainers/image-spec)\n\n### Docker V2\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\n### OCI Image Format\n\nThe OCI image format is a specification for container images based on the\nDocker Image Manifest Version 2, Schema 2 format. Artifact Registry implements the\n[OCI Specification](https://github.com/opencontainers/distribution-spec/blob/main/spec.md), an API protocol to help\nstandardize distribution of content.\n\nYou can store artifacts that support the OCI image format in\nArtifact Registry Docker repositories. For example:\n\n- [Helm 3 charts](https://helm.sh/docs/topics/registries/) can be packaged in OCI format. For more information, see the Artifact Registry [Helm overview](/artifact-registry/docs/helm).\n- Singularity supports pulling\n [Docker and OCI images](https://docs.sylabs.io/guides/3.10/user-guide/singularity_and_docker.html) from private\n registries and pushing and pulling images in\n [Singularity Image File](https://github.com/apptainer/sif) (SIF) format with private\n registries.\n\n - Authentication is similar to authentication for [Docker clients](/artifact-registry/docs/docker/authentication). Singularity can read settings that the credential helper added to the Docker client `config.json`. If you are using a token or service account key for password authentication, you can use the [singularity remote login](https://docs.sylabs.io/guides/3.10/user-guide/cli/singularity_remote_login.html) command to log in with your credentials.\n - Use the [singularity pull](https://docs.sylabs.io/guides/3.10/user-guide/cli/singularity_pull.html) command with the `oras://` URI to pull images.\n - Use the [singularity push](https://docs.sylabs.io/guides/3.10/user-guide/cli/singularity_push.html) command with the `oras://` URI to push images.\n\n For example, the following command pulls `my-app:latest` from the repository\n `us-west1.pkg.dev/my-project/sif-repo`. \n\n singularity pull oras://us-west1.pkg.dev/my-project/sif-repo/my-app:latest`\n\n### Manifest lists and image indexes\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\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."]]
