Skip to content

Saved Images FAQ

View as Markdown

What is the difference between a saved image and a snapshot?

Section titled “What is the difference between a saved image and a snapshot?”

A saved image is a reusable template: launch new nodes from it whenever you want a copy of that setup. A snapshot saves one node as it is at that moment. To use it, save it as an image and launch a node from that image. See Saved images and snapshots.

Any node can, GPU nodes included, except firewall and spot nodes. See Save a node as an image.

Do I need to power the node off before saving an image?

Section titled “Do I need to power the node off before saving an image?”

It depends on the family, as listed in Node families. C3, M3, SDC3, GDC3, E1, and E1WC nodes can save while the node is running. Every other family, including GDC, needs it powered off first. See Save a node as an image.

Does a saved image include my attached volumes?

Section titled “Does a saved image include my attached volumes?”

No. Saving an image copies only the node’s root disk. If the setup you want to reuse depends on data in a volume, recreate or reattach that volume on each node you launch. See Save a node as an image.

Can I launch a node from a saved image in a different region?

Section titled “Can I launch a node from a saved image in a different region?”

Yes, once you move the image there. Export it to a bucket in the other region, then import the file in that region. See Move the image to the other region.

You can import qcow2, qed, raw, vdi, and vhd images, with a single boot partition and no larger than 2,048 GB (2 TB). See Import a custom image.

Can I export a saved image to Object Storage?

Section titled “Can I export a saved image to Object Storage?”

Yes, when the image’s region is Delhi or Chennai. The image must be in Ready or Available state, and the access key needs Bucket Admin or Bucket Writer permission. See Export an image to Object Storage.

Why does an imported image use more space than the file I uploaded?

Section titled “Why does an imported image use more space than the file I uploaded?”

An imported image is stored in a format specific to E2E, and can use up to five times its original file size. Importing itself is free; you are charged for the storage the image uses. See Import a custom image.

Yes. Upload the disk image to an E2E Object Storage bucket, then import it from the Saved Images page. Before you make the image, install and turn on the OpenNebula context package on the source machine and turn off cloud-init, or nodes launched from it cannot be reached. See Import a custom image, and for an AWS EC2 instance, Migrate an AWS EC2 instance to E2E.

Yes, from the image’s Actions menu on the Saved Images page. Delete works once the image has finished creating, exporting, or being cloned, is not in Error, and no scale group uses it. See Troubleshooting Saved Images if it is refused.

Can I move a saved image to another project?

Section titled “Can I move a saved image to another project?”

Yes, to another project in the same account. Before you move it, remove its tags, and make sure the image is not in Error and no scale group uses it. It keeps its region, and you can launch nodes from it in its new project. See Move a saved image to another project.

Does moving a saved image move its node too?

Section titled “Does moving a saved image move its node too?”

No. The node the image was taken from stays in its project. To move the node together with its saved images, move the node instead. See Move a node to another project.