I have rebuilt everything from scratch again today, and can reproduce this very scary scenario every time.
Setup - Clean install of 24.04, with an encrypted pool. Install an app, where you are required to choose a pool, so I choose my unlocked pool, and it creates ix-applications unencrypted.
This then prevents you from unlocking the pool in the GUI.
Anything else I can check, or should I raise as a bug?
Thanks
CC
It’ll just get shot down, since what you see happening is by design.
You’ll probably be told “Don’t encrypt the root dataset of a newly created pool.”
They’ve already made enforcements in the middleware to (attempt to) prevent unencrypted datasets from being nested below an encrypted parent.
What happened in tandem is forcing the “ix-applications” dataset to be unencrypted. So unlike “iocage” in Core, you cannot encrypt your “Apps” dataset; nor do they want you to nest it underneath an encrypted root dataset.
If anything, the resolution to this “bug” will likely be “If the root dataset is encrypted, then it cannot house your Apps. You’ll have to pick a different pool.”
Don’t give them any ideas. 
Really? So I missed that best practice - dont encrypt your pool; encrypt child datasets - I somehow missed that one! Not easy to fix either without migrating the data off and on again. Nightmare.
Appreciate the quick response - will now need to consider if the Juice is worth the squeeze…
Thanks
CC
