InvokeAI virtual machine

Last update: October 05 2026Open in Markdown

InvokeAI Virtual Machine is a preconfigured cloud server with a tool for creating and processing images using AI technologies.

The image from which the server is deployed contains:

• InvokeAI — a tool for creating and processing images using AI technologies;

• Docker — a platform for running containerized applications;

• Docker Compose — a tool for running multi-container applications in Docker;

• nginx — a web server and reverse proxy;

• drivers required to work with graphic processing units (GPU).

Before creating a server, review the software license agreements included in the image.

Functionality

• generation and processing of images using built-in and external ML models;
• image generation from text descriptions (text-to-image);
• creation of image generation workflows.

Minimum resource requirements

Number of vCPUs	4
RAM	8 GB
Boot volume	80 GB
GPU	Required

Getting started with InvokeAI Virtual Machine

1. Create a cloud server with InvokeAI.

2. Run InvokeAI.

1. Create a cloud server with InvokeAI

1. In the Control Panel, in the top menu, click Products and select AI Marketplace.

2. Click Create server.

3. Fill in the blocks:

   • Name and placement;
   • Source;
   • GPU;
   • Configuration;
   • Disks;
   • Network;
   • optional: Access;
   • optional: Additional settings;
   • optional: Automation.

4. Check the server price.

5. Click Create server.

Name and placement

1. Enter the server name.

2. Select the location where the server will be created. The list of available GPUs depends on the location. You cannot change the location after creating the server.

Source

Select the image InvokeAI VM (Ubuntu 24.04 LTS 64-bit).

GPU

1. Click Add GPU.

2. Select the GPU type. When selecting a GPU, consider the minimum resource requirements for running the image. For GPU specifications and descriptions, see the Graphics processing units (GPUs) instructions.

3. Specify the number of GPUs.

After the server is created, you can change the type and number of GPUs or remove the GPU. For more information, see the Change cloud server configuration instructions.

Configuration

1. Specify the number of vCPUs.

2. Specify the RAM size.

After the server is created, you can change the configuration.

Disks

1. Select the boot disk type. When using a local disk as a boot disk, GPUs are unavailable.

2. Specify the disk size in GB or TB. The maximum size for all network volumes is 10 240 GB (10 TB), for a local disk — 1 256 GB (1 TB).

3. If you selected the Universal SSD v2 or Fast SSD v2 disk type, specify the total number of read and write operations in IOPS. After creating the disk, you can change the number of IOPS — decrease or increase it. The number of IOPS changes is unlimited.

4. Optional: to add additional disks:

   4.1. Click Add disk.

   4.2. Select the volume type.

   4.3. Specify the disk size in GB or TB. The maximum size for all network volumes is 10 240 GB (10 TB), for a local disk — 1 256 GB (1 TB).

   4.4. If you selected the Universal SSD v2 or Fast SSD v2 disk type, specify the total number of read and write operations in IOPS. After creating the disk, you can change the number of IOPS — decrease or increase it. The number of IOPS changes is unlimited.

   After the server is created, you can detach additional disks from it or attach new ones.

Network

You can add the server to a new or existing subnet. The subnet can be:

• private without internet access. You will not be able to connect to the server from the internet, including via SSH or RDP;
• private with one public IP address. A static public IP address is connected to the server's private address via a cloud router. The server will be accessible from the internet via this public IP address;
• public, where all addresses are accessible from the internet.

Private subnetwork without internet access

1. To add a server to an existing private subnet:

   1.1. In the Subnet field, select an existing subnet.

   1.2. Optional: change the default private IP address of the server.

2. To create a new private subnet:

   2.1. In the Subnet field, select the subnet type Private.

   2.2. Optional: change the subnetwork CIDR.

   2.3. Optional: enable the DHCP toggle. For more information about the DHCP protocol, see the Selectel blog post How the DHCP protocol works.

   2.4. Optional: change the default gateway IP address.

   2.5. Optional: change the network in which the subnet will be created — you can select an existing network or create a new one. If you are creating a new network, enter the network name.

Private subnetwork with a public IP address

1. If you already have a private subnetwork and a cloud router with internet access:

   1.1. In the Subnet field, select the subnet type Private + 1 public IP.

   1.2. In the Private field, select an existing subnet.

   1.3. Optional: change the default private IP address of the server.

2. If you want to create a new subnet and a cloud router with internet access, in the Subnet field, select the subnet type Private + 1 public IP.

   A private network nat, a router router-nat, and one public IP address will be created automatically. The server will be added to the subnet in the nat network.

Public subnetwork

1. To add a server to an existing public subnet:

   1.1. In the Subnet field, select an existing subnet.

   1.2. Optional: change the default public IP address of the server.

2. To create a new public subnet:

   2.1. In the Subnet field, select the subnet type Public.

   2.2. In the Subnet size field, select the subnet size.

Optional: Access

1. In the Password for "root" field:

   1.1. Copy the password for the root user — a user with unrestricted permissions for all system actions.

   1.2. Save the password in a secure place and do not share it in plain text.

2. Place an SSH key for the project on the server for secure connection:

   2.1. If the SSH key has not been added to the Cloud Platform, click , enter a key name, paste the public key in OpenSSH format, and click Add.

   2.2. If the SSH key has been added to the Cloud Platform, in the SSH key field, select an existing key.

Optional: Additional settings

1. To create a preemptible server, select the Preemptible server checkbox.

2. If you plan to create multiple servers and want to increase infrastructure fault tolerance, add the server to a placement group:

   2.1. To create a new group, click , enter a group name, and select a placement policy on different hosts:

   • soft—the system will try to place the servers on different hosts. If no suitable host is available when creating the server, it will be created on the same host;

   • hard—servers in the group are required to be placed on different hosts. If no suitable host is available when creating the server, the server will not be created.

   2.2. If the group has been created, in the Placement group field, select a placement group.

3. To add additional information or filter servers in the list, add server tags. A tag with the image name is added automatically. To add a new tag, in the Tags field, enter a tag.

Optional: Automation

1. To add a script that will be executed using the cloud-init agent during the first operating system boot, in the User data field:

   • open the Text tab and paste the script as text;
   • or open the File tab and upload the script file.

   For script examples and supported formats, see the User data instructions.

2. Launch InvokeAI

1. In the control panel, in the top menu, click Products and select AI Marketplace.

2. On the InvokeAI Virtual Machine card, click Go to GUI.

3. Enter the username — admin.

4. Enter the password — server UUID. You can copy it in the control panel: in the top menu, click Products → AI Marketplace → in the server menu, select Copy UUID.

5. Click Log in.