Skip to main content
Last updated on

Artifact Registry

Beta

This feature is in Beta. To use it, a workspace admin must turn on Databricks Artifact Registry from the Previews page. See Manage Databricks previews. Databricks will announce pricing for Artifact Registry when it becomes generally available.

Artifact Registry stores container images as governed assets in Unity Catalog. Use it to push images with standard Docker commands, control access with Unity Catalog privileges, and make images available to supported Databricks workloads.

Key concepts​

  • Artifact: A named container image stored in Unity Catalog, identified by a three-level name in the format catalog.schema.artifact.
  • Tag: A mutable alias that points to an artifact version using the format catalog.schema.artifact:tag. Pushing a tag again can change the version that the tag resolves to. For repeatable deployments, avoid mutable tags such as latest and reference a digest when the workload accepts digest references.
  • Image digest: An immutable, content-addressed identifier for a specific version of an artifact.
  • Image acceleration: An optimization that Databricks applies automatically after you push an eligible image to Artifact Registry. This process converts the image to a format designed to reduce pull latency for supported workloads. To check an artifact version's image acceleration status, see Check image acceleration status.

How Artifact Registry works​

Publishers and users work with container images in Artifact Registry through the following lifecycle:

  1. Build and push: A publisher builds an image, tags it with a three-level Unity Catalog name in the format catalog.schema.artifact:tag, and pushes it to the workspace registry. See Artifact name requirements and Push an image.
  2. Govern: Artifact Registry stores the image under the specified Unity Catalog catalog and schema. Unity Catalog privileges control who can publish, discover, and read the image. See Grant permissions.
  3. Discover: Users call the Software Artifacts API to discover available images and versions and to check image acceleration status. See Discover images and versions.
  4. Use: Users reference an image when they create supported Databricks workloads, such as jobs that run custom container images.

Diagram of a publisher pushing an image to Artifact Registry, where Unity Catalog governs it before a user discovers and uses it.

Limitations​

The following limitations apply:

  • Availability:

    • Artifact Registry is available in the following regions:

      • asia-south1
      • asia-southeast1
      • europe-west1
      • europe-west2
      • europe-west3
      • us-central1
      • us-east1
      • us-east4
      • us-west1

  • Supported use:

    • You can use images in Artifact Registry only with supported Databricks workloads.
    • You cannot use Docker or another registry client to pull these images or download image blobs directly.

  • Authentication:

    • The workspace OAuth access token used for Docker authentication expires after one hour. A push that takes longer can fail authorization for a layer uploaded after expiration. Retry the push so that the Docker credential helper requests a new token.

  • Image acceleration:

    • Images larger than 30 GB cannot be converted for image acceleration.
    • Image acceleration does not expose a failed conversion state. See Check image acceleration status.

  • Discovery and management:

    • Catalog Explorer does not provide an interface for images.
    • The registry endpoint does not support Open Container Initiative (OCI) tag-list requests or delete requests.
    • The Software Artifacts API returns at most 10 tags for a version when more than 10 tags point to the same digest.

  • Artifact names:

Additional resources​

On this page