Release dependency

20 views
Skip to first unread message

b.og...@gmail.com

unread,
Mar 15, 2019, 12:13:32 PM3/15/19
to iocage
Hi,

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.
What i'm talking about :
jailhouse ~ # zfs list -t all -o name,clones zroot/iocage/releases/11.1-RELEASE/root@dbjail1
NAME                                             CLONES
zroot
/iocage/releases/11.1-RELEASE/root@dbjail1  zroot/iocage/jails/dbjail1/root
jailhouse
~ # zfs list -t all -o name,origin zroot/iocage/jails/dbjail1/root                
NAME                             ORIGIN
zroot
/iocage/jails/dbjail1/root  zroot/iocage/releases/11.1-RELEASE/root@dbjail1

I created this jail some times ago, what I pasted above implies that:
  • If i do want to send let's say zroot/iocage/jails/dbjail1/root@FULL-20190315 to another zpool, i do have to send the clone too
  • I can't remove the zroot/iocage/releases/11.1-RELEASE dataset even if that same jail has been upgraded to 12.0 now
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

Brandon Schneider

unread,
Mar 21, 2019, 2:21:33 PM3/21/19
to b.og...@gmail.com, iocage
That is because the default jail type is a clone jail. Using the latest (1.1) release, you can choose to create a thickjail that will free you from that dependency (with the cost of space). Thick basejails are a good compromise between these problems.
-Brandon


--
You received this message because you are subscribed to the Google Groups "iocage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iocage+un...@googlegroups.com.
To post to this group, send email to ioc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/iocage/f61139fd-9a1b-4ff4-9cdb-d07e7bea52ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

b.og...@gmail.com

unread,
Mar 22, 2019, 1:59:41 PM3/22/19
to iocage
Damn totally missed that part of the last doc...
Sorry, and again thanks for the good work.

Bastien

Brandon Schneider

unread,
Mar 22, 2019, 2:00:21 PM3/22/19
to b.og...@gmail.com, iocage
No problem! Thanks for the kind words :)
-Brandon


Reply all
Reply to author
Forward
0 new messages