i might actually make the unhinged container engine concept i was thinking abt that has a hard dependency on zfs

the build spec is a list of steps and each is done in incremental layers
right
seems reasonable
so instead of using overlayfs for the incrementality you just use zfs snapshots

if another container relies on existing layers you clone the snapshot for that layer

you can also now squash containers by just deleting all snapshots for a dataset

and get this you can distribute the individual layers or any combination of layers a client is missing using regular zfs send/recv

there's probably security issues with accepting arbitrary zfs recvs but if it's a system designed for my personal usage it's fine right

Sign in to participate in the conversation
📟🐱 GlitchCat

A small, community‐oriented Mastodon‐compatible Fediverse (GlitchSoc) instance managed as a joint venture between the cat and KIBI families.