Incus: No uid/gid allocation configured

Incus
21 
incus project list
+-------------------+--------+----------+-----------------+-----------------+----------+---------------+--------------------------------+---------+
|       NAME        | IMAGES | PROFILES | STORAGE VOLUMES | STORAGE BUCKETS | NETWORKS | NETWORK ZONES |          DESCRIPTION           | USED BY |
+-------------------+--------+----------+-----------------+-----------------+----------+---------------+--------------------------------+---------+
| Talos             | YES    | YES      | YES             | YES             | YES      | YES           | Talos-based Kubernetes cluster | 11      |
+-------------------+--------+----------+-----------------+-----------------+----------+---------------+--------------------------------+---------+
| default (current) | YES    | YES      | YES             | YES             | YES      | YES           | Default Incus project          | 12      |
+-------------------+--------+----------+-----------------+-----------------+----------+---------------+--------------------------------+---------+
| test              | YES    | YES      | YES             | YES             | NO       | NO            |                                | 3       |
+-------------------+--------+----------+-----------------+-----------------+----------+---------------+--------------------------------+---------+

The issue already occured when there was only the default project though.

22

Thanks, I’ll take a look. It really doesn’t make sense for us to hit that logic when in an unrestricted default project. It would make a bit of sense if it was a restricted project as we do use some limited uid/gid mapping in that case, even for VMs, but in your environment, we really shouldn’t be.

23