I cannot run rockylinux 9 cloud VM

I’m getting wired issue: Instance rl9-vm: This virtual machine image requires an agent:config disk be added

my configruation:

architecture: x86_64
  image.architecture: amd64
  image.description: Rockylinux 9 amd64 (20240329_02:06)
  image.os: Rockylinux
  image.release: '9'
  image.requirements.cdrom_agent: 'true'
  image.serial: '20240329_02:06'
  image.type: disk-kvm.img
  image.variant: default
  volatile.apply_template: create
  volatile.base_image: ddab050dcd76b5e4a7e995959144789ae5d7ebba5295ad53d7c78512b13e6e12
  volatile.cloud-init.instance-id: 3b5d34ab-08be-41c2-aff5-a6e980e63fc8
  volatile.eth0.hwaddr: 00:16:3e:5a:fe:c4
  volatile.uuid: 4b060764-aa13-45e3-8f5c-00aa1c7addf8
  volatile.uuid.generation: 4b060764-aa13-45e3-8f5c-00aa1c7addf8
    path: /
    pool: default
    size: 64GiB
    type: disk
ephemeral: false
  - default
stateful: false
description: ''
created_at: '2024-03-29T21:33:20.06805906Z'
name: rl9-vm
status: Stopped
status_code: 102
last_used_at: '1970-01-01T00:00:00Z'
location: none
type: virtual-machine
project: default

You need an extra disk, something like that under devices:

    type: disk
    source: agent:config

thank you
Isn’t that should be out-of-box by Incus (or UI)?

I thinking of create PR to fix that issue in LXD UI but I don’t think they will accept it because it specific for Incus only

It only applies to specific versions of specific images, the vast majority of our images do not need the extra drive. In general Incus has a policy of treating images as untrusted so we don’t ever want a property of an image to cause automatic changes to instance configuration, which is why we instead have it report an error message and let the user perform the change if they believe it’s correct to do.

how I can determine if the image need it or not?

The image will have a restriction for cdrom_agent set in its properties.