Images¶
The Images tab catalogs the OS images and snapshots you can boot a VM from. Three categories: stock images (curated by Cloud Digit), custom images (built or imported by you), and snapshots (instant point-in-time captures).
Overview¶
The Images tab — your project's image catalog.
Columns:
| Column | What it shows |
|---|---|
| Name | Image name |
| Type | Stock / Custom / Snapshot |
| OS | e.g. Ubuntu 24.04 LTS, Rocky Linux 9, Windows Server 2025 |
| Size | Disk size (GiB) — also the minimum boot-disk size for VMs launched from it |
| Status | Active, Queued (uploading), Saving, Error |
| Visibility | Project, Shared, Public |
| Created | Relative timestamp |
A filter row at the top lets you switch between All / Stock / Custom / Snapshots.
Administration¶
Quotas¶
Project Settings → Quota:
- Custom images — count cap (default 50)
- Total image storage — GiB cap across custom images and snapshots
- Snapshots per volume — rolling count cap (default 100)
Stock-image refresh policy¶
Stock images are updated monthly by Cloud Digit:
- Latest of each major version (
ubuntu-24.04) is replaced in-place with the newest patched build - Previous versions remain available with an
-oldsuffix for 90 days then are retired - CIS-hardened variants for Ubuntu and Rocky are kept current on the same monthly cadence
You can pin to a specific point-in-time stock image by copying it to your custom-image catalog — that copy is yours forever.
Image sharing¶
A custom image can be shared across projects in the same organization. Click an image → Sharing → + Share to project → pick the target project + grant level (launch-only or launch + edit). Cross-organization sharing is on the roadmap.
Operation¶
Creating a custom image¶
Three ways:
From a running VM¶
Servers → pick a VM → Snapshot. The platform creates a snapshot of the VM's root disk and promotes it to an image in one step. The VM keeps running; the snapshot is read at the hypervisor level.
From a snapshot¶
Volumes → pick a snapshot → Promote to image. Useful when you've been iterating on a data-disk snapshot and want to turn it into a launchable boot image.
From an uploaded file¶
+ Create image → Upload. Accepted formats:
.qcow2(most common; QEMU's native format).raw.vmdk(VMware).vhd/.vhdx(Hyper-V)
Cloud Digit converts to qcow2 internally on upload. Up to 50 GiB per upload; larger images should be uploaded via the API as multipart.
The Packer-based "build it once, snapshot it, push to the catalog" pattern is the recommended workflow — see the Packer + Terraform reference.
Launching from an image¶
In the Create Server flow, pick the image from the Image dropdown. The VM's boot disk inherits the image's minimum size unless you override.
Sharing across projects¶
Detail panel → Sharing tab → manage which sibling projects can launch from this image.
Deleting¶
Delete removes the image from the catalog and frees the storage. Snapshots that have been promoted to images stay around until the image itself is deleted.
Stock-image catalog¶
The current stock set:
| Family | Versions |
|---|---|
| Ubuntu | 22.04 LTS, 24.04 LTS |
| Debian | 12 (bookworm) |
| Rocky Linux | 9 |
| AlmaLinux | 9 |
| Windows Server | 2019, 2022, 2025 |
| RHEL | 9 (BYOS — bring your own subscription) |
| Cloud Digit AI | Ubuntu 24.04 + NVIDIA driver + CUDA 12.x + PyTorch / JAX / vLLM pre-installed |
| CIS-hardened | Ubuntu 22.04/24.04, Rocky 9 (OpenSCAP-scored) |
Image specifics — naming conventions, login defaults, cloud-init compatibility — match what's documented under Virtual Machines → Stock images.
Troubleshooting¶
| Symptom | Likely cause | Fix |
|---|---|---|
Upload stuck at Queued | File > 50 GiB or unsupported format | Use the API with multipart upload, or convert to qcow2 first |
Status Error after upload | Format auto-detect failed or file is corrupt | Re-upload; if reproducible, check qemu-img info locally and confirm format |
| VM won't boot from custom image | virtio drivers missing | Ensure your image has virtio-blk, virtio-net, virtio-scsi, and cloud-init baked in |
| Snapshot promotion to image times out | Source volume very large + project storage quota tight | Free space; retry; or split the volume |
| Cannot share to another project | You don't have Project Admin on the target | Get the target project to invite you, or grant from their side |
| Image still listed after delete | Cache lag (≤ 30 s) | Hit the top-bar Refresh button |
Pricing¶
Custom-image storage is billed at Object Storage (Archive) rates. Stock images don't count against your quota.
Related¶
- Snapshots & Custom Images — underlying service
- Servers — where images are launched
- Volumes — what snapshots originate from
- Object Storage (Archive) — backing store