Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
© 2022 Yandex.Cloud LLC
Yandex Container Registry
  • Getting started
  • Step-by-step instructions
    • All instructions
    • Authenticating in Yandex Container Registry
    • Managing a Docker image
      • Getting information about available 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
    • Managing Helm charts
      • Getting information about available Helm charts
      • Pushing a Helm chart to a registry
      • Pulling a Helm chart from a registry
      • Deleting a Helm chart from a registry
    • Managing a registry
      • Getting information about existing registries
      • Creating a registry
      • Updating a registry
      • Deleting a registry
    • Managing a repository
      • Getting information about existing repositories
    • Managing policies for automatically deleting Docker images
      • Getting information about existing lifecycle policies
      • Creating a lifecycle policy
      • Updating a lifecycle policy
      • Performing lifecycle policy dry runs
      • Deleting a lifecycle policy
    • Scanning Docker images for vulnerabilities
    • Working with roles
      • Assigning a role
      • Viewing assigned roles
      • Revoking a role
  • Yandex Container Solution
  • Practical guidelines
    • All tutorials
    • Running a Docker image on a VM
    • Setting up automatic scanning of a Docker image
  • Concepts
    • Overview
    • Docker image
    • Docker volume
    • Registry
    • Repository
    • Docker policies for automatically deleting Docker images
    • Vulnerability scanner
    • Backups
    • Quotas and limits
  • Access management
  • Pricing policy
  • API reference
    • Authentication in the API
    • gRPC
      • Overview
      • ImageService
      • LifecyclePolicyService
      • RegistryService
      • RepositoryService
      • ScannerService
      • OperationService
    • REST
      • Overview
      • Image
        • Overview
        • delete
        • get
        • list
      • LifecyclePolicy
        • Overview
        • create
        • delete
        • dryRun
        • get
        • getDryRunResult
        • list
        • listDryRunResultAffectedImages
        • listDryRunResults
        • update
      • Registry
        • Overview
        • create
        • delete
        • get
        • list
        • listAccessBindings
        • listIpPermission
        • setAccessBindings
        • setIpPermission
        • update
        • updateAccessBindings
        • updateIpPermission
      • Repository
        • Overview
        • delete
        • get
        • getByName
        • list
        • listAccessBindings
        • setAccessBindings
        • updateAccessBindings
        • upsert
      • Scanner
        • Overview
        • get
        • getLast
        • list
        • listVulnerabilities
        • scan
  • Troubleshooting
  • Questions and answers
  1. Step-by-step instructions
  2. Managing a Docker image
  3. Pulling a Docker image from a registry

Pulling a Docker image from a registry

Written by
Yandex.Cloud

    To pull a Docker image, you need to know the repository it is stored in and its tag or digest.

    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/crpd50616s9a2t7gr8mi/ubuntu:hello
        hello: Pulling from crpd50616s9a2t7gr8mi/ubuntu
        84ed7d2f608f: Already exists
        be2bf1c4a48d: Already exists
        a5bdc6303093: Already exists
        e9055237d68d: Already exists
        Digest: sha256:035ac8e1bd9c49871a2fd76ccb3c4b0f84e7eee775919ccd345337ec7b49f80d
        Status: Downloaded newer image for cr.yandex/crpd50616s9a2t7gr8mi/ubuntu:hello
        
      • Using the digest:

        $ docker pull cr.yandex/crpd50616s9a2t7gr8mi/ubuntu@sha256:035ac8e1bd9c49871a2fd76
        ccb3c4b0f84e7eee775919ccd345337ec7b49f80d
        sha256:035ac8e1bd9c49871a2fd76ccb3c4b0f84e7eee775919ccd345337ec7b49f80d: Pulling from crpd50616s9a2t7gr8mi/ubuntu
        84ed7d2f608f: Already exists
        be2bf1c4a48d: Already exists
        a5bdc6303093: Already exists
        e9055237d68d: Already exists
        Digest: sha256:035ac8e1bd9c49871a2fd76ccb3c4b0f84e7eee775919ccd345337ec7b49f80d
        Status: Downloaded newer image for cr.yandex/crpd50616s9a2t7gr8mi/ubuntu@sha256:035ac8e1bd9c49871a2fd76ccb3c4b0f84e7eee775919ccd345337ec7b49f80d
        

        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
      REPOSITORY                                                        TAG                 IMAGE ID            CREATED             SIZE
      cr.yandex/crpd50616s9a2t7gr8mi/ubuntu   <none>              50ff4b0e5783        24 hours ago        86.7MB
      ubuntu                                                            latest              1d9c17228a9e        2 weeks ago         86.7MB
      

    Was the article helpful?

    Language / Region
    © 2022 Yandex.Cloud LLC