LXC on promox 4
- Thread starter Terence
- Start date
I don't think containers would ever support anything other than kernel-supported filesystem or block device based "disks". If there was a qcow2 kernel driver block device driver then the answer would be probably yes, but I don't remember such one existing.
If you really insist you can possibly try not-so-fast or not-so-reliable stuff like anything fuse based, for example http://ask.xmodulo.com/mount-qcow2-disk-image-linux.html. They are possibly need some fiddling since proxmox don't support them out of the box (or, possibly, at all).
Disclaimer: I haven't tried them.
I would rather try stuff like zfs (which I don't personally trust but people keep telling it's cute) or btrfs (which still doesn't feel very stable but YMMV), both can do tricks on storage like compression or deduplication, among other things.
If you really insist you can possibly try not-so-fast or not-so-reliable stuff like anything fuse based, for example http://ask.xmodulo.com/mount-qcow2-disk-image-linux.html. They are possibly need some fiddling since proxmox don't support them out of the box (or, possibly, at all).
Disclaimer: I haven't tried them.
I would rather try stuff like zfs (which I don't personally trust but people keep telling it's cute) or btrfs (which still doesn't feel very stable but YMMV), both can do tricks on storage like compression or deduplication, among other things.
) sparse.
Note that even raw files are sparse in that unused blocks are not actually allocated. Also note that the loopback driver will turn discards into "hole punching", which essentially means running fstrim inside a container may reduce the amount of physical space consumed by the .raw file.