Feature or enhancement request details
container root filesystems and named volumes use AFPS files containing sparse ext4 disk images.
If a container runs long enough and unlinks files along the way, more and more of the sparse image will show as in use on the host, even for fs blocks that are free after previously having been used.
Virtualization Framework will recover blocks that the guest trims using the FSTRIM ioctl
We should:
- Determine the UX for cleaning up containers and volumes. For this issue we should start simple and build from there.
Code of Conduct
Feature or enhancement request details
containerroot filesystems and named volumes use AFPS files containing sparse ext4 disk images.If a container runs long enough and unlinks files along the way, more and more of the sparse image will show as in use on the host, even for fs blocks that are free after previously having been used.
Virtualization Framework will recover blocks that the guest trims using the
FSTRIMioctlWe should:
Code of Conduct