Failed to create certificate "admin": Certificate already in trust store

I attempted installing IncusOS on a Proxmox VM to test it out, but I keep getting this error after the install completed:

image

I can’t find this error anywhere on the internet. TPM 2.0 is on, Secure Boot is on, everything should be perfectly fine with my VM configuration. What did I do wrong?

That was with an image downloaded from https://incusos-customizer.linuxcontainers.org?

It looks like you’ve got Incus half-initialized, as if the system booted, managed to load the certificate and maybe some other stuff into Incus and then failed after that before it could record that it did the first time initialization.

So then when starting again, it fails because the entry already exists.

I forgot to remove the ISO image after first boot and had to remove it and reset the VM. Maybe that was it? And yes, it was an image from the official website, with a certificate from my host, installed following the guide, except that I used q35 instead of i440fx.

Actually, turns out the error returned before is that apparently no free network subnet was found, and then it goes to that error. I use 10.0.0.0/8 for network, and DHCP uses 10.0.128.1-10.0.192.254. I wasn’t able to get a screenshot of it before Incus restarted.

Hmm, what mask do you have for your network?

10.0.128.1 - 10.0.192.254 would probably be fine if it’s defined as a /17 covering 10.0.128.1 through 10.0.255.254.

But if the mask is set as /8, it would completely prevent Incus from allocating a local bridge with a non-overlapping subnet, causing the error.

1 Like

I have a /8. I didn’t realize that would brick my install. Would it be possible to allow setting the bridge subnet manually via the custom ISO downloader network settings?

You can untick the Apply defaults and then configure network, storage and default profile by hand.

But also having a /8 broadcast domain is usually a pretty bad idea, so you may want to reconsider that :slight_smile:

After manual configuration, it worked perfectly! Except there was no storage pool, and I couldn’t add one without adding another disk. When I read the docs, apparently there was supposed to be a “local” storage pool. There’s absolutely no storage pools. However, there was a mention of a “local” ZFS pool in the storage config. I added it as a storage pool, but it’s kinda weird that it wasn’t created by default. Is this a bug, or just a side effect of not using the defaults?

incus storage create local zfs source=local/incus

… that’s what i did??? I was asking if it was a bug that it wasn’t created by default, since it seemed unusual that the docs claimed that it was by default.

incusbr0, the local Incus storage pool, the default profile entries and the backups, images and logs storage volumes are what the apply defaults control.

Oh, okay.