Skip to content

Images Console

Reference · Updated Sep 2026

Coming from another cloud?

▸AWS·Amazon Machine Images (AMIs)

Amazon Machine Images (AMIs)high

  • Managed via EC2 APIs, not Glance.
  • Region-specific with cross-region copy.
  • Marketplace AMIs may charge hourly fees.
  • Includes block device mapping in AMI.
AWS docs ↗
▸Azure·Compute Gallery image definitions and versions

Azure Compute Gallery image definitions and versionshigh

  • 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.
Azure docs ↗
▸DigitalOcean·Images (Distributions, 1-Click Apps, Snapshots, Backups, Custom Images)

Images (Distributions, 1-Click Apps, Snapshots, Backups, Custom Images)high

  • 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'.
DigitalOcean docs ↗
▸Google Cloud·Machine Images (full VM state capture)

OS imageshigh

  • 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.
Google Cloud docs ↗
▸Hetzner·Images

Imageshigh

  • 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.
Hetzner docs ↗

Images console

Overview#

Images are pre-configured files that contain a virtual machine's (VM) operating system and associated data. Images serve as templates for creating instances (VMs) within the Compute service. The Image console is responsible for managing and providing access to these images.

Select Compute > Images to display the images console.

Images console showing Current Project Images tab (empty) and Public Images tab with available OS images including Ubuntu, Rocky, CirrOS, and CoreOSClick to zoom
Images console with Current Project Images and Public Images tabs

The console lists all images in your project under the Current Project Images tab.

You can edit and delete images.

You launch an instance based on an image.

You can create a volume based on an image.

Select an image to view image details, security associated with the image, and custom properties associated with the image.

Images details#

You may encounter other custom properties or metadata associated with specific images, depending on how they are configured by the image creator.

Property/AttributeDescription
NameA human-readable name for the image, used for identification purposes.
IDA unique identifier automatically assigned to the image by OpenStack when it is created.
StatusIndicates the current state of the image, such as queued, saving, active, or deleted.
VisibilityDetermines who can access the image. It can be set to public or private.
ProtectedA boolean value indicating whether the image is protected from deletion.
Disk FormatSpecifies the format of the image, such as raw, qcow2, vmdk, or iso.
Container FormatDescribes the container format of the image, such as bare, ovf, or aki.
SizeThe size of the image file in bytes.
ChecksumA hash value used to verify the integrity of the image file.
TagsA list of user-defined tags that can be associated with the image.
Min DiskThe minimum disk size (in GB) required to boot the image.
Min RAMThe minimum amount of RAM (in MB) required to boot the image.
ArchitectureIndicates the architecture for which the image is built, such as x86_64 or arm.
Kernel IDFor images that require an external kernel, this attribute specifies the ID of the kernel image.
Ramdisk IDFor images that require an external ramdisk, this attribute specifies the ID of the ramdisk image.
OwnerThe ID of the project or user that owns the image.
Created AtThe timestamp indicating when the image was created.
Updated AtThe timestamp indicating when the image was last updated.

Default images#

Go to Compute > Images > Public Images to view the list of available default images. The us-east-1 catalog as of 20.05.2026 (per openstack image list against project 5462) ships nine images. Use the hyphenated image name (Ubuntu-24.04, not Ubuntu 24.04) when launching instances; the space form is not in the Glance catalog.

  • Ubuntu-24.04 (LTS, Noble): general-purpose Linux image with virtio-scsi and vif_multiqueue_enabled for enhanced performance. Recommended default for new instances. Source: cloud-images.ubuntu.com

  • Ubuntu-22.04 (LTS, Jammy): previous LTS release with virtio-scsi and vif_multiqueue_enabled. Source: cloud-images.ubuntu.com

  • Rocky-9: RHEL-compatible Linux image with virtio-scsi and vif_multiqueue_enabled. Source: dl.rockylinux.org

  • Rocky-10: current Rocky Linux major release. Source: dl.rockylinux.org

  • AlmaLinux-9: second RHEL-compatible distribution alongside Rocky. Source: almalinux.org/get-almalinux

  • AlpineLinux-3.23: minimal musl/busybox image; small footprint, fast boot, common base for container builders and CI runners. Source: alpinelinux.org/downloads

  • Cirros-0.6.2: lightweight test image for sanity testing and CI pipelines. Boots in seconds; not suitable for real workloads. Source: download.cirros-cloud.net

  • FedoraCoreos-38: minimal, auto-updating container host. Magnum Kubernetes cluster templates use it (Standard-v2.0-k8s-calico-fc38_v*); readers typically do not boot it directly outside a cluster context. Source: builds.coreos.fedoraproject.org

  • OpenClaw-Latest: Quake AI's OpenClaw runtime image, used by the OpenClaw app template in the Apps console. See Deploy OpenClaw.

Images service#

Images service CLI reference#

Image service is backed by OpenStack Glance. For details on how Quake AI implements OpenStack, see How Quake AI uses OpenStack.

Images service API reference#

See also#

Quick answers

Was this page helpful?