there were a number of containers immune to 'docker rm', seemed it was trying to invoke 'zfs delete' on something that had already been removed (presumably mome

there were a number of containers immune to 'docker rm', seemed it was trying to invoke 'zfs delete' on something that had already been removed (presumably moments ago as part of a previous step). Nasty workaround was to manually recreate the dataset (and children) so that it could remove them. The issue was common enough that I could google it so don't stress. More worryingly, 'prune' locked up for about 10 minutes before getting to do it's thing. pinning the cpu the whole time. This was on my devbox, so maybe it's my doing but did not inspire confidence. I've run FreeBSD ZFS for about a decade and openzfs/ubuntu in prod for kafka clusters so I'm no stranger - this docker usage was just particularly strange.