First of all, thanks for the great work :).
I have some questions about jails creation and the fact that every jail is dependant to the release it was created with, I don't really understand why does iocage keep that dependancy all along.
jailhouse ~ # iocage create -r 11.0-RELEASE -n test2 -b
jailhouse ~ # iocage upgrade -r 12.0-RELEASE test2
jailhouse ~ # zfs list zroot/iocage/releases/11.0-RELEASE/root@test2
NAME USED AVAIL REFER MOUNTPOINT
zroot/iocage/releases/11.0-RELEASE/root@test2 0 - 984M -
jailhouse ~ # iocage destroy -r 11.0-RELEASE
This will destroy RELEASE: 11.0-RELEASE
Are you sure? [y/N]: y
11.0-RELEASE has dependent jails (who may also have dependents), use --recursive to destroy:
test2
My point is that I feel kindof "stuck" with this 11.1-RELEASE, only because of that clone.
Now of course i can always
zfs snapshot zroot/iocage/jails/test2/root@1
zfs send zroot/iocage/jails/test2/root@1 | zfs recv zroot/iocage/jails/test2/root2
zfs destroy -r zroot/iocage/jails/test2/root
zfs rename zroot/iocage/jails/test2/root2 zroot/iocage/jails/test2/root
to have my jail totally independant but why do i have to do all of this for every jail ?
Also, i do use iocage for a long time for now and sometimes when i destroy a jail, this same snapshot on the release remains forever, until I delete it manually, is that a known bug ? I may be doing something wrong cause i can't reproduce right now weirdly.
Am i right or am i doing something wrong ?
I did read the doc a lot of times but feel free to rtfm my face if i actually missed something.
Cheers,
Bastien