Problem/Justification
I would like the ix-virt dataset to be exposed to the UI.
This would make it easier (especially for users newer to incus) to understand what it’s doing under the hood. Currently TrueNAS silently creates the dataset and stores new container volumes and templates there.
In the UI it says that there is something stored on the pool that takes x gigabytes but it doesn’t tell you where or what it is used for. Even when they go into the shell and search for it they can’t really find it. Not even with ls -a. This is especially bad for downloaded templates since there is (I think) currently no way to remove them via the UI.
It would additionally allow to set custom properties to the dataset like a separate snapshot schedule or compression method.
Another nice feature would be that when creating a new container the user gets to choose in which dataset the container disk gets stored (Similar to how it’s working for VMs in EE). Also another thing I would find useful is to limit the size a container volume can grow to. Proxmox already allows these things via it’s UI.
Impact
The change to expose the dataset to the UI would make things more clear and would allow people to choose compression or snapshot timing independently from the rest of the pool.
This would probably be a simple fix.
Limiting the size of a container disk is already supported by incus (I think the size property does exactly that) so it would probably also just have to be exposed to the UI.
User Story
Personally I found the current behavior confusing so I would guess other users would fall into the same trap when the next release gets out of the nightly stage.
I use the feature to limit container disk size all the time in proxmox and think it’s a very useful feature.