Akasha.
DocsAbout instancesCreate an instance

Create an instance

How to create a container or virtual machine from a catalog image, a custom ISO, an uploaded instance file, or an OCI registry image.

You create instances from the console. You need permission to create instances in the target project; if you don't have it, the Create instance button is disabled with a tooltip.

To open the form, go to Instances → Create instance.

Name and description

The instance name is optional — if you leave it empty, a name is generated for you. If you set one, it must:

  • be 1–63 characters long,
  • contain only letters, digits, and hyphens,
  • start with a letter,
  • be unique within the project (the form checks for duplicates as you type).

The description is free text.

Choose a base image

Every instance needs a base image. The form offers four sources:

Browse images

Click Browse images to pick from images in your project together with the public image catalog (catalog availability depends on your deployment). Filter by search text, OS, release, variant, architecture, and type (Any, Container, VM). Some images are container-only or VM-only; selecting one locks the Instance type field accordingly. See Use images.

Use a custom ISO

Click Use custom ISO to boot a VM from an installer ISO you uploaded earlier (see Custom ISOs). Selecting an ISO:

  • forces the instance type to VM,
  • attaches the ISO as a disk device,
  • pins the instance's location to where the ISO volume lives.

With an ISO source only Create is offered (not Create and start). After creation, open the instance's Console tab to run the OS installer — the success notification includes an Open console shortcut.

Upload an instance file

Click Upload instance file to create an instance from a file. Two modes:

  • Backup archive (.tar.gz) — an instance backup previously exported from Akasha. Choose the file, a new instance name (derived from the file name by default), and a root storage pool.
  • External disk format — a VM disk image in .img, .qcow, .qcow2, .vdi, .vhdx, or .vmdk format. Choose the instance name, target location, root storage pool, and image architecture, plus two conversion options: Convert to raw format (unchecked automatically if the file is already raw) and Add Virtio drivers (required if the image does not already have Virtio drivers installed).

Uploads show a progress bar; large files can take a while.

Use an OCI image

Click Use OCI and enter a Registry URL and an Image name to create an application container directly from an OCI registry. The result appears in the list as Container (App).

Instance type, location, and profiles

  • Instance type — Container or VM. Auto-set and locked when the chosen image supports only one type.
  • Location — on deployments with multiple servers, you can target a specific cluster member or group, or leave it to the scheduler. Project policy can block member targeting.
  • Profiles — one or more profiles whose configuration the instance inherits; default is preselected.

All other configuration sections (devices, resource limits, cloud-init, and so on) are available in the left menu once an image is selected, and match the sections described in Configure instances. You can also flip the footer switch to edit the full configuration as YAML.

Root disk requirement

The instance must have a root disk — either defined explicitly in the Disk section or inherited from a profile. If neither is present, submission is blocked and the form jumps to the Disk section so you can add one.

Create the instance

The footer offers two buttons (enabled once an image is selected and validation passes):

  • Create — creates the instance and leaves it Stopped.
  • Create and start — creates the instance and starts it immediately.

You are returned to the instance list right away; the new instance appears as a Setting up row while creation runs, and notifications report the result. If creation fails, the failure notification includes a Check configuration action that reopens the form with your previous values and highlights the failing section.

Cancel a creation in progress

While an instance is still Setting up, click Cancel operation on its row in the instance list to abort the creation. You can also cancel it from the Operations page — see Troubleshoot instances.