Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Container Registry
  • Getting started
    • All guides
    • Installing and configuring Docker
    • Authentication in Container Registry
      • Getting information about existing Docker images
      • Creating a Docker image
      • Pushing a Docker image to a registry
      • Pulling a Docker image from a registry
      • Deleting a Docker image from a registry
    • Scanning Docker images for vulnerabilities
    • Creating a trigger for a registry
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Troubleshooting
  • FAQ
  1. Step-by-step guides
  2. Managing a Docker image
  3. Pulling a Docker image from a registry

Pulling a Docker image from a registry

Written by
Yandex Cloud
Updated at August 29, 2024

To download a Docker image, you need the container-registry.images.puller role or higher. In addition, you need to know which repository houses the Docker image, as well as its tag or hash.

To work with Docker images, install and configure Docker.

CLI
  1. Select the Docker image you need. To do this, get a list of Docker images in the registry.

  2. Pull the Docker image from the registry:

    • Using the tag:

      docker pull cr.yandex/<registry_ID>/ubuntu:hello
      

      Result:

      hello: Pulling from crpd50616s9a********/ubuntu
      84ed7d2f608f: Already exists
      be2bf1c4a48d: Already exists
      a5bdc6303093: Already exists
      e9055237d68d: Already exists
      Digest: sha256:035ac8e1bd9c49871a2fd76ccb3c4b0f84e7eee775919ccd345337ec********
      Status: Downloaded newer image for cr.yandex/crpd50616s9a********/ubuntu:hello
      
    • Using the digest:

      docker pull cr.yandex/<registry_ID>/ubuntu@sha256:035ac8e1bd9c49871a2fd76
      

      Result:

      ccb3c4b0f84e7eee775919ccd345337ec7b49f80d
      sha256:035ac8e1bd9c49871a2fd76ccb3c4b0f84e7eee775919ccd345337ec********: Pulling from crpd50616s9a********/ubuntu
      84ed7d2f608f: Already exists
      ...
      e9055237d68d: Already exists
      Digest: sha256:035ac8e1bd9c49871a2fd76ccb3c4b0f84e7eee775919ccd345337ec********
      Status: Downloaded newer image for cr.yandex/crpd50616s9a********/ubuntu@sha256:035ac8e1bd9c49871a2fd76ccb3c4b0f84e7eee775919ccd345337ec********
      

      Note that in this case the Docker image will be pulled with no tag. The TAG field value will be <none>.

  3. Make sure the Docker image has been pulled:

    docker image list
    

    Result:

    REPOSITORY                                  TAG     IMAGE ID      CREATED       SIZE
    cr.yandex/crpd50616s9a********/ubuntu       <none>  50ff********  24 hours ago  86.7MB
    ubuntu                                      latest  1d9c********  2 weeks ago   86.7MB
    

See alsoSee also

  • Troubleshooting in Container Registry.

Was the article helpful?

Previous
Pushing a Docker image to a registry
Next
Deleting a Docker image from a registry
© 2025 Direct Cursus Technology L.L.C.