You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, during the deployment process we use zfs clone to make a new VM, or a Jail. This means that the deployment process will be almost instant, but sometimes it's not ideal in terms of disk space usage. I won't go into much detail here, but essentially the more you deviate from the base image - the more space your clone takes.
This is fine on most systems, but can be problematic on the systems with fast NVME drives, but with much less space overall. The underlying process will rely on ZFS replication executed locally from the template dataset to the target dataset.
The text was updated successfully, but these errors were encountered:
As of now, during the deployment process we use
zfs clone
to make a new VM, or a Jail. This means that the deployment process will be almost instant, but sometimes it's not ideal in terms of disk space usage. I won't go into much detail here, but essentially the more you deviate from the base image - the more space your clone takes.This is fine on most systems, but can be problematic on the systems with fast
NVME
drives, but with much less space overall. The underlying process will rely onZFS replication
executed locally from the template dataset to the target dataset.The text was updated successfully, but these errors were encountered: