@brendan@social.brendans-bits.com
Post #2637298
2026-02-12 16:29 UTC
@drwx@mastodon.acc.sunet.se The way I think of 'thick' vs 'thin' is whether the jail has its own copy of root and how it is upgraded.
A thick jail has a copy of the base system to itself. Any changes to the base system affect that jail only. You have to upgrade the base of each jail individually.
A thin jail shares the base amongst multiple concurrent jails. Any changes to base affect all jails. You can upgrade the base of multiple jails simultaneously by upgrading the shared base.
Replies (2)
-
@brendan@social.brendans-bits.com 2026-02-12 16:42
@drwx@mastodon.acc.sunet.se If I read your question correctly, I would say "yeah nah... a cloned snapshot is sort of... but really isn't a thick jail" "Yeah..." because it like a thick jail in that you have resource isolation: you have a jail that isn't sharing base with another jail. Any changes to the jail built on the clone are stored separately to the snapshot. But I come down on the side of "nah" because you don't have portability: you can't simply pick up that jail and move it to another host.
-
@drwx@mastodon.acc.sunet.se 2026-02-16 12:45
@brendan@social.brendans-bits.com Ok, this brings a little more clarity.