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
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Cloud Registry
  • Getting started
    • Overview
    • Registry
      • Overview
      • Docker image
      • Java artifact
      • Node.js artifact
  • Access management
  • Pricing policy
  • CLI reference
  • Audit Trails events
  1. Concepts
  2. Artifacts
  3. Docker image

Docker image in Yandex Cloud Registry

Written by
Yandex Cloud
Improved by
amatol
Updated at December 16, 2024

A Docker image is a template for creating Docker containers. It is an executable package that contains everything you need to run an application: code, runtime environment, libraries, environment variables, and configuration files.

A Docker image consists of layers. Each change is written to a new layer.

  • When pushing or pulling a Docker image, operations are performed only on the layers that were changed.

  • The layers of the source Docker image are shared by all its versions and are not duplicated.

Version controlVersion control

Docker image version control is carried out using tags and digests.

A tag is assigned by the user. A tag must be unique within one registry and can be edited. If no tag is specified, Docker CLI assigns the latest tag by default while pushing a Docker image to the registry.

Warning

The tag latest doesn't mean that the Docker image was the latest one pushed.

We don't recommend overwriting tags. Use a unique tag for each Docker image version. This way you can use the same Docker image version on all your VMs with identical specifications and more easily identify causes of problems.

A Docker image can have multiple tags. If you push a new version of the Docker image with an existing tag, it's reused: it gets deleted from the old Docker image version and written to the new one.

A digest is generated automatically, is unique, and identifies the exact version of a Docker image.

You can access a specific Docker image version in one of the following ways:

  • <registry>/<image_name>:<tag>
  • <registry>/<image_name>@<digest>

The Docker image and all its versions are stored in a registry.

See alsoSee also

  • Java artifact
  • Node.js artifact

Was the article helpful?

Previous
Overview
Next
Java artifact
Yandex project
© 2025 Yandex.Cloud LLC