Templates Troubleshooting

Title	Description	Related Issues
Custom tpl create-from-image keeps timing out	Two common root causes: (1) the custom image does not start the HTTP service configured by --probe / --probe-path (for an envd-based image, this is commonly 49983/health); (2) the host is in a nested-virt environment (e.g. AWS EC2) — missing instruction-set bits (XSAVE family) panic the MicroVM, and doubled VM-exits on page faults slow the in-guest agent enough to blow VsockServerReady / probe budget. Fixes: verify the configured HTTP probe locally; follow the Custom Template Images tutorial when the image needs envd; switch to PVM deployment to avoid nested virt.	#312, #95, #94, #161, #253
Template build fails due to insufficient disk space	Building a template requires unpacking the OCI image and writing it to disk, which consumes a lot of temporary space. When the partition holding /tmp, /data/cubelet or /usr/local/services/cubetoolbox/ runs low, the template can stall at UNPACKING / BUILDING_EXT4, or surface as mkfs.ext4 errors such as directory block checksum mismatch or "Ext2 inode is not a directory".	#240, #251
Template Creation Times Out When the Sandbox CIDR Overlaps the LAN	The one-click deployment defaults the sandbox network to 192.168.0.0/18. If the host LAN also uses 192.168.1.x, Cube may allocate sandbox IPs that overlap the physical network, causing template creation or port probing to fail with context deadline exceeded. Change the Cubelet CIDR to a non-overlapping range and remove the old TAP devices plus cube-dev before restarting.	Guide