Antsle Forum
Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more.
Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked.
Could not zfs clone for antlet - removing antlet via command line
You may get an error message 'Could not zfs clone for antlet <antlet_name>' when creating a new antlet if a zfs file system exists with the same name. This may happen if a previously deleted antlet (with the same name) was not removed properly.
An antlet is made of three basic parts: an xml definition, a zfs file system, and its directory and files.
To view your antlets and status run
virsh list --all or virsh -c lxc:/// list --all
for lxc antlets use the '-c lxc:///' option
So to stop an antlet you can use
virsh shutdown ANTLET_NAME or virsh -c lxc:/// shutdown ANTLET_NAME
'shutdown' is a graceful shutdown. Use 'destroy' to force the shutdown (like pulling the plug).
To remove the antlet xml use
virsh undefine ANTLET_NAME --managed-save or virsh -c lxc:/// undefine ANTLET_NAME --managed-save
And remove zfs file system:
find the zfs path with
zfs list
The path should mimic the directory path.
Remove the file system with
zfs destroy path/ANTLET_NAME
Note: there is no leading '/' in the zfs path
If you get a 'Data set busy' error, then you may need to remove the directory first
rm -rf /antlets/ANTLET_NAME
replace /antlets/ with the path to your antlet