This is a follow up question on Is it possible to mount nested ZFS datasets from within a container?.
I followed the steps in that thread to create a container. Host OS and container OS are a Bookworm 12 and ZFS version of 2.2.7 or 2.1.11, Incus latest 6.9. Tested on two different environments.
Working with nested ZFS datasets is a great feature and allows you manage them like you would do on the host. However, there is a small issue with managing snapshots of the “root” dataset. You are allowed to create snapshots (inclusive recursive) inside the container but accessing them afterwords fails:
root@u1:~# zfs snapshot pool/incus/custom/default_u1-extra@bah
root@u1:~# zfs list -t snapshot
NAME USED AVAIL REFER MOUNTPOINT
pool/incus/custom/default_u1-extra@bah 0B - 96K -
root@u1:~# zfs destroy pool/incus/custom/default_u1-extra@bah
could not find any snapshots to destroy; check snapshot names.
So far I haven’t found a way to work around the problem from inside the container. Tried to add zfs allow properties or changing perms etc. but no joy. I believe this is an Incus security feature to not allow access outside the mounted dataset?
Given that you are allowed to create snapshots you should be able to access / manage them as they belong to the mounted dataset. On the other hand this conflicts with snapshots created on the host level. Any possiblity to allow accessing snapshots from inside the container?