base_image_size is effectively the max size of the thinpool snapshot,
and this is static (does not resize). If you are running containers
with larger individual layers, this will fail. (elastic is a good test
for this).
The thinpool should be 10GB, not 1GB (to align with the .img's defined
earlier in file).
Fixes: #266
Signed-off-by: Eric Ernst <eric.ernst@intel.com>
This setup scripts have been using cri-o all this while as the pod
controller/manager system. Recent past cri-o has had some issues with
kata-deploy (A restart of the service will not be able to re-connect
with the existing pods and restart all of them including kata-deploy,
which will hit an endless loop). Moving to containerd as default for
now.
Firecracker cannot be used with a released version of containerd as
there is no default block based snapshotter available today. If you wish
to use cri-o make sure you set `RUNNER=crio` in your environment prior
to using the script.
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
Eric Ernst