Skip to content

Images

The Linux images instances launch from, their aliases and login users, and how an alias picks an image.

Updated View as Markdown

An image is a bootable disk that an instance’s root volume is copied from. You launch by an alias, such as linux/ubuntu:24.04, that always names the current image of that release. In the console, open Compute, then Images; from the CLI, ezgh compute images list and ezgh compute images get <alias>.

Image Alias Login user
Ubuntu 24.04 LTS linux/ubuntu:24.04 ubuntu
Ubuntu 26.04 LTS linux/ubuntu:26.04 ubuntu
Debian 13 linux/debian:13 debian
Debian 12 linux/debian:12 debian
Rocky Linux 10 linux/rocky:10 rocky
Rocky Linux 9 linux/rocky:9 rocky
Alpine Linux 3.24 linux/alpine:3.24 alpine
Ubuntu 26.04 LTS (EZGH Optimized) linux/ezgh-ubuntu:26.04 ubuntu
Ubuntu 24.04 LTS (EZGH Optimized) linux/ezgh-ubuntu:24.04 ubuntu
Debian 13 (EZGH Optimized) linux/ezgh-debian:13 debian
Debian 12 (EZGH Optimized) linux/ezgh-debian:12 debian
Rocky Linux 10 (EZGH Optimized) linux/ezgh-rocky:10 rocky
Rocky Linux 9 (EZGH Optimized) linux/ezgh-rocky:9 rocky

The stock images are the distributions’ own cloud images, published by EZGH Cloud. Every image runs cloud-init, which installs your SSH keys for the login user, and none has a password login. All are amd64.

EZGH Optimized Images

The linux/ezgh-* images are the stock images above with EZGH’s guest agents already installed: the Fleets agent, the Observability agent, the QEMU guest agent and, on Ubuntu and Debian, the VPC addresses hook. The agents stay idle until you give them access. See EZGH Optimized Images.

Aliases and images

EZGH Cloud checks each distribution for a new release of its cloud image every week, verifies it against the distribution’s published checksum (and signature, where the distribution signs it), and moves the alias to it. A launch uses the image the alias names at that moment, so a new instance starts from the latest image; existing instances aren’t changed.

A launch can also name an exact image by its ID (img_…) instead of an alias: one of the project’s own images, or a public EZGH image, for instance to pin the image an alias names today. Such an instance records no alias; its root volume’s source still names the image.

An alias’s page in the console lists its current images. An image’s page shows how it was verified (Signed or Checksum only), its SHA-256, the source URL and upstream serial it came from, its size, minimum disk size, format, boot mode and login user (Default user). The volume an instance launched with records the exact image in its source (image, imageSha256).

Root volume size

The root volume is at least the image’s minimum disk size, rounded up to a whole GiB; the console proposes 20 GiB or that minimum, whichever is larger. A larger root volume is grown into by cloud-init at first boot.

Errors

Error When
404 alias_not_found No such alias
404 image_not_found No such image ID that this project may launch, or it isn’t available
400 architecture_mismatch The image’s architecture isn’t the instance type’s
400 root_volume_too_small rootVolume.sizeGiB is below the image’s minimum
Navigation

Type to search…

↑↓ navigate↵ selectEsc close