I realize containers are experimental, so, if anything, hopefully this will help solve a bug.
I just recently upgraded to the latest stable version (25.04.2.6). After rebooting, I unlocked all of my pools and datasets. Then I went to the “Apps” tab and started those (everything was fine).
But then I went to my “Containers” tab. I saw “Dataset Is Locked” even though I’ve unlocked all of my datasets and pools. At that point, I should’ve been able to go into the “Global Settings” and toggle the pool but when I tried to do that, all I got was a spinner in the “Pools” dropdown.
I’ve attempted to run incus from the command line to recover the configuration but that’s also giving me an error.
The .ix-virt dataset exists on the pool I originally chose (as shown by zfs list) and it’s mount point is specified as legacy which, from what I’ve seen elsewhere, is correct for incus to auto-mount when it needs it.
It’s also the case that when I hover over the “Go To Dataset” button in the UI, the correct path is shown in the tooltip. Of course when I click on it, it just goes to the base “Dataset” page since that dataset is not visible in the UI.
Anyone have any thoughts on troubleshooting this? I really don’t want to have to recreate my containers and even if I did, I wouldn’t want this to happen next time I reboot.