Copy a running Kiste into a new, independent Kiste in seconds.
A fork copies the disk of a running Kiste into a new Kiste. The copy is made with copy-on-write, so it takes seconds regardless of the disk's size, and from then on the two are independent: changes in one never show up in the other.
The fork boots fresh from the copied disk: files and installed packages are there, the source's running processes are not.
It keeps the source's size, environment and checkpoint interval.
It does not inherit the source's automatic stop. Give it its own with
--ttl:A checkpoint of the source is taken before it is copied.
The fork becomes your current Kiste.
Forks count as Kisten for your limits.
To copy a stopped Kiste, or a past state of one, restore a snapshot instead.
Typical uses: try a risky upgrade without touching the original; give each of several agents its own copy of a prepared Kiste; keep a pristine setup and fork it for every task.