Deleteing Fangtooth dataset .ix-virt after moving back to ElectricEel

I tried upgrading my TrueNAS ElectricEel-24.10.2 to Fangtooth the other day. I ran into trouble with my VMs (I know, Instances is experimental, but I wanted to try it.).
My original VM zvol resides on volume2/VMs/docker-tanj8o.
I created an Instance for my Docker VM, choosing to copy the data over, instead of moving it. It didn´t work very well, and I decided to go back to ElectricEel.

Now I have a dataset called volume2/.ix-virt taking up some space, and I would like to delete it.
The VM is what is taking up space. It is stored here:
volume2/.ix-virt/custom/default_docker-tanj8o

Running into new issues, and hoping someone can guide me through it.
First I tried to delete it via the GUI, and got an error message about snapshots, clones, etc. So I moved to the shell.

When I run this: zfs destroy volume2/.ix-virt/custom/default_docker-tanj8o

I get this response:

cannot destroy 'volume2/.ix-virt/custom/default_docker-tanj8o': volume has children
use '-r' to destroy the following datasets:
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-10_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_01-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@incus_1747125920
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-08_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-07_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_09-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_06-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_10-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_00-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-01_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-11_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_07-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_08-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-12_23-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-06_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-09_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-05_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_04-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-02_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-12_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-04-29_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_03-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-04-30_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_05-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-04_23-00-2w
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-13_02-00-12hrs
volume2/.ix-virt/custom/default_docker-tanj8o@auto-2025-05-03_23-00-2w

So, working through that list, I only get three rows down, and then, running this:
zfs destroy volume2/.ix-virt/custom/default_docker-tanj8o@incus_1747125920

I get this response:

cannot destroy 'volume2/.ix-virt/custom/default_docker-tanj8o@incus_1747125920': snapshot has dependent clones
use '-R' to destroy the following datasets:
volume2/VMs/docker-tanj8o@auto-2025-05-20_08-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-20_07-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-17_23-00-2w
volume2/VMs/docker-tanj8o@auto-2025-05-18_23-00-2w
volume2/VMs/docker-tanj8o@auto-2025-05-20_10-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-20_00-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-19_23-00-2w
volume2/VMs/docker-tanj8o@auto-2025-05-16_23-00-2w
volume2/VMs/docker-tanj8o@auto-2025-05-20_06-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-20_09-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-20_01-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-20_02-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-20_05-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-19_23-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-15_23-00-2w
volume2/VMs/docker-tanj8o@auto-2025-05-13_23-00-2w
volume2/VMs/docker-tanj8o@auto-2025-05-20_03-00-12hrs
volume2/VMs/docker-tanj8o@auto-2025-05-14_23-00-2w
volume2/VMs/docker-tanj8o@auto-2025-05-20_04-00-12hrs
volume2/VMs/docker-tanj8o

Now, at the end of this list, it is demanding that I delete the original VM dataset.
I would like to delete the volume2/.ix-virt dataset, without losing my docker VM. I feel a little stuck, and hope someone knows a solution to this.

Ok, so here´s what I did.
I turned my VM off
I took a snapshot of the dataset I didn´t want to lose, which is th dataset acting as disk for that VM:

volume2/VMs/docker-tanj8o

Then I replicated the snapshot to another host.
Now as I ran my zfs destroy, the dataset mentioned above was deleted. And all snapshots associated with it.

Replicated the dataset(snapshot) back into place and booted my VM. Worked fine. Not exactly straight forward, but at least I got rid of the stuff ix-virt dataset which was bugging me.

Before doing this, I tried promoting the clone of docker-tanj8o, but couldn´t because reasons. So then I took this route. Now it is solved at least.