How to create an instance snapshot
Coming from another cloud?
▸AWS·Amazon Machine Images (AMIs)
Amazon Machine Images (AMIs)
- Managed via EC2 APIs, not Glance.
- Region-specific with cross-region copy.
- Marketplace AMIs may charge hourly fees.
- Includes block device mapping in AMI.
▸Azure·Compute Gallery image definitions and versions
Azure Compute Gallery image definitions and versions
- Organized in galleries with image definitions and versioned images (Microsoft.Compute/galleries/images/versions), more structured than flat Glance images.
- Supports global replication to regions with replicas (up to 100), ZRS storage, unlike OpenStack's store-only model.
- Sharing via RBAC, community galleries, or direct share; requires gallery setup vs simple OpenStack image sharing.
- New features like Trusted Launch only in Gallery, legacy managed images deprecated.
▸DigitalOcean·Images (Distributions, 1-Click Apps, Snapshots, Backups, Custom Images)
Images (Distributions, 1-Click Apps, Snapshots, Backups, Custom Images)
- DigitalOcean classifies images into specific types (snapshots, backups, applications/1-Click, distributions, custom) rather than OpenStack Glance’s more generalized image model with visibility/properties/metadata.
- Custom images are imported by providing a URL to a supported disk format (raw, qcow2, vhdx, vdi, vmdk) and have a documented max decompressed size (100 GB), which differs from typical OpenStack flows where images are uploaded directly to Glance and size limits are operator-defined.
- DigitalOcean image operations are through /v2/images in their API, not Glance (and images also include DigitalOcean-specific fields like kind values base/snapshot/backup/custom/admin).
- DigitalOcean's "applications" images (1-Click Apps/Marketplace style) are a first-class image type, whereas OpenStack commonly treats such preconfigured stacks as separate concerns (OpenTofu modules, Heat templates, app catalogs) rather than an image 'type'.
▸Google Cloud·Machine Images (full VM state capture)
OS images
- Public images shareable across projects (e.g. debian-cloud); OpenStack typically tenant-private.
- Image families point to latest version; no OpenStack equivalent.
- Custom images stored in Cloud Storage with licensing fees for premium OS.
▸Hetzner·Images
Images
- Includes system images (OS), user images (snapshots/backups).
- API /v1/images; create via server action create_image (type=snapshot/backup).
- Billed per GB/month; backups cost 20% of server price.
- No direct image upload; custom via ISO attach or rebuild.
How to create an instance snapshot
Create a point-in-time snapshot of a running instance. Snapshots are stored as images and can be used to launch new instances or create golden images for repeatable deployments.
Prerequisites
- ConsoleLogged in to the Quake AI console
- CLIOpenStack CLI installed and authenticated (
clouds.yamloropenrcsourced) - APIAPI token generated with
$OS_TOKENand service endpoint variables set
Windows: CLI examples use bash. Set up a Linux CLI environment on Windows before proceeding.
Snapshots count against your project's storage quota. Ensure you have enough free storage; for example, a 10 GB volume instance requires approximately 10 GB of free quota.
Before you begin#
Some base images require updates before a snapshot can be created successfully. If you are using the shared Ubuntu 22.04 image, see Update Ubuntu 22.04 for snapshots before proceeding.
Create the snapshot#
Use a snapshot to create a golden image#
A golden image is a baseline image configured to your standards that you reuse to launch other instances.
- Create a new instance from a base image.
- Update and configure the instance as needed (packages, security hardening, application setup).
- Create a snapshot using any method above. Use a descriptive name like
golden-ubuntu2204-v1.
The snapshot is now available as an image source when creating new instances.
Create a new instance from a snapshot#
Verify the result#
See also#
- How to back up and restore a Quake AI VM: snapshot, offsite copy, and restore drill
- Compute API Reference: full parameter documentation for the Compute API
- Instance snapshots concepts
- Instance snapshots console
- Snapshots CLI reference
- Snapshots API reference
- How to create an instance
Usage Guidelines
The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.
For the full policy, see Usage Guidelines.
Last validated: 25.05.2026
Quick answers
- Why does `openstack image save` write a 0-byte file for my boot-from-volume instance?CLI
- Why does `openstack server create` fail with "Only volume-backed servers are allowed for flavors with zero disk"?CLIAPITerraform
- Why does my project still have a 10 GiB Cinder volume after I deleted my instance?CLIAPI