Images
An image is a complete copy of the file system structure and data on a disk.
It is designed to quickly create a data disk, primarily, a VM boot disk. Images can be used for distributing software, e.g., OS distributions or disks with pre-installed software.
You can use images with outdated OS versions on your VMs; however, you will not be able to get support for these VMs if you have any issues.
Tip
To regularly back up your data on disks, use snapshots.
You can create an image from a disk, snapshot, or another image. If you have an image file, you can import it to Yandex Cloud.
You can use the management console to create images of network SSDs and HDDs. To create an image of a non-replicated SSD or an ultra high-speed network storage with three replicas (SSD), use the CLI, Terraform, or API.
When you create a Windows boot disk image, specify this in the operating system type. This is important for proper CPU emulation and calculating resource usage costs.
The supported formats include Qcow2
, VMDK
, RAW
, and VHD
.
Image family
If you regularly update your images, you can group them into families. You can use the family name to find the latest image in the family.
Warning
All images belonging to the same family must be in the same folder.
Let's assume you want to upload an image of your operating system to Yandex Cloud. When creating an image, specify a family, e.g.,
best-linux-distro
. This will allow other users to get the latest version of your operating system by specifying the family and image folder ID in the request.
Public images
Note
The terms and conditions of technical support for public images may differ. For more information, see the product page in Yandex Cloud Marketplace.
Public images are, e.g., products and solutions from Yandex Cloud Marketplace.
You can learn how to get a list of public images here.
To make your image available to other Yandex Cloud users, grant them public access to it. To do this, assign the compute.images.user
role to the All authenticated users
public group. However, the compute.images.user
role does not grant permission to delete or edit your image.
Images optimized for deployment
The feature is at the Preview stage.
Note
You can migrate both optimized and non-optimized images.
Use optimized images only if you have a lot of disks and deployments.
An image can be optimized for frequent VM deployments. This speeds up the deployment of VMs and enables you to quickly expand your computing power and use the relevant tools from your own image.
Fast deployment is achieved by using multiple layers for storing data in a storage. The first layer stores the image source data, while the second one stores user data. When creating VM disks from optimized images, the first layer is reused rather than copied to a new storage location every time. Disks created from optimized images run on VMs in the same way as disks created from regular images: they can be used as boot disks and are fully available for data storage. The performance of these disks does not differ from that of regular ones.
Regular images from Cloud Marketplace are already optimized for deployment. To optimize your image, select the Optimize for deployment option when uploading the image.
By default, optimized images have a zero quota. To increase the quota
See also
- Learn how to create a VM from a custom or public image.
- Preparing your disk image
- Importing an image from another cloud or folder
- Configuring image access permissions