You can create a private image from an instance created as required, and use this image to launch more instances with the same operating system, pre-installed software, and related configurations as the original instance.
To ensure data integrity, only instances in the "Stopped" status are supported for creating private images.
You must ensure that the image and cloud disk snapshot quotas are sufficient, because if the instance system disk is a cloud disk or the instance attaches a data disk, it will take up the private image quotas and the cloud disk snapshot quotas.
Note: * For the Linux system, if the instance configures the automatic attachment command of the data disk in /etc/fstab or configures 70-persistent-net.rules in /etc/udev/rules.d, please delete it before producing private images, or the instance based on private image creation may not be able to be started normally. * If the current instance's system disk is local disk, then the created private image is local system disk image; If the current instance's system disk is cloud disk, then the created private image is cloud system disk image. You can convert a local system disk image to a cloud system disk image by [Image Type Conversion](//docs.jdcloud.com/en/virtual-machines/convert-image). * If the machine mounts a data disk of local disk (e.g. GPU instance type machine), because the local data disk does not support manufacturing snapshot, in this case, the manufactured private image will not be able to include the local data disk.
Access Virtual Machines Console to enter the instance list page. Or access JD Cloud Console Click navigation bar on the left Elastic Compute - Virtual Machines - Instance to enter the instance list page.
In the pop-up window of create images, supplement the "Name" and "Description" of the private image，click OK to start the creation of the private image.
In addition to backing up the system disk, you can choose a data disk currently attached to the backup instance to create an image. The data disk will be associated with the system disk image in the form of a snapshot and displayed in the "Device Mapping Information" on the private image detail page. The "Device Mapping Information" will be the preset configuration of the data disk for instance creation using this private image, which makes it easy to quickly deploy the entire VM. If you want to modify the capacity of the data disk, you can adjust it when you create a VM based on that image. Click here for details on the data disk Device Name Assignment Rules.
It takes a long time to make the entire image that contains data of system disk and data disks. In order to avoid the failure, please stop other operations on the VM and the cloud disk during the production process, and ensure that the current instance and the cloud disk snapshot have sufficient quotas.
The submitted private image is created successfully into "Available" status after passing through the two intermediate statuses of "Pending" and "Replicating", then it can be used normally. In the intermediate status, operations of Share, Create instance, and Delete on the image are not allowable.
In the process of image creating, any resource's failed creation will cause the image to be in the "Error" status. If data disks attached to the instance are selected to create the image that contains data of system disk and data disks, all the snapshots created by the operation will be automatically deleted after the operation failed, but the private image could be deleted after your confirmation.