CloudSOE publishes operating system images for KubeVirt, the virtual machine add-on for Kubernetes. The same images work on OpenShift Virtualization, which is built on KubeVirt.

This guide starts a VM from a containerdisk: a container image that holds a VM disk. It is the fastest way to a running VM, because the cluster pulls the disk like any other image.

What you’ll need

  • A Kubernetes cluster with KubeVirt installed, on amd64 nodes with hardware virtualisation
  • kubectl and virtctl
  • An SSH public key

Step 1: Pick an image

ImageLatest versionReleasedFormatsArchVerifyUse
quay.io/cloudsoe/debian-12Debian12202611.15.02026-11-15containerdiskqcow2amd64Digest · SHA-256How to use →
quay.io/cloudsoe/debian-13Debian13202611.15.02026-11-15containerdiskqcow2amd64Digest · SHA-256How to use →
quay.io/cloudsoe/ubuntu-24.04Ubuntu24.04202611.14.02026-11-14containerdiskqcow2amd64Digest · SHA-256How to use →
quay.io/cloudsoe/ubuntu-26.04Ubuntu26.04202611.15.02026-11-15containerdiskqcow2amd64Digest · SHA-256How to use →

Each image is the distribution’s official cloud image, unmodified. It has no default password. You pass a user or an SSH key through cloud-init when you create the VM.

Step 2: Create the VM

Save this as ubuntu-24-04.yaml and replace the SSH key with your own:

apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  name: ubuntu-24-04
spec:
  runStrategy: Always
  template:
    spec:
      domain:
        cpu:
          cores: 1
        memory:
          guest: 2Gi
        devices:
          disks:
            - name: rootdisk
              disk:
                bus: virtio
            - name: cloudinit
              disk:
                bus: virtio
          interfaces:
            - name: default
              masquerade: {}
      networks:
        - name: default
          pod: {}
      volumes:
        - name: rootdisk
          containerDisk:
            image: quay.io/cloudsoe/ubuntu-24.04:202611.14.0
        - name: cloudinit
          cloudInitNoCloud:
            userData: |
              #cloud-config
              ssh_authorized_keys:
                - ssh-ed25519 AAAA... [email protected]
kubectl apply -f ubuntu-24-04.yaml
kubectl get vmi ubuntu-24-04 --watch

The VM is ready when the phase is Running. The first start takes longer while the node pulls the image, which is about 600 MB.

Step 3: Log in

cloud-init adds your key to the image’s default user. On Ubuntu that user is ubuntu.

virtctl ssh ubuntu@vm/ubuntu-24-04

If SSH does not answer, open the serial console to watch the boot:

virtctl console ubuntu-24-04

Set a user and password instead

For a lab VM where you want console login, replace the userData. The password is set for the default user:

            userData: |
              #cloud-config
              password: change-me
              chpasswd:
                expire: false
              ssh_pwauth: true

What a containerdisk does not do

  • The disk is ephemeral. Changes are lost when the VM stops. For a VM that keeps its data, import the image to a persistent disk.
  • The disk is the size of the cloud image, a few gigabytes. A persistent disk can be any size you request.

Pin the image

A tag such as 202611.14.0 identifies one build. For a deployment that must not change, reference the digest shown on the image page:

          containerDisk:
            image: quay.io/cloudsoe/ubuntu-24.04@sha256:448ee9b20a67b02450e5c17507e8a8c440d6d91b8ad69609326496e458de669c

The latest tag follows the newest build.

Next steps