Another question regarding this empty space. When you backup a container via proxmox pve, does it clear the empty space before the compression (like with the dd conv=sparse option) or does it copy the whole image?
Thanks
I said hacky because using size=0 for containers does not work in the web interface and it doesn't look documented for the command line either (at least I couldn't find it).
If the su bug is fixed, does that mean that containers would operate normally? I mean just like with the raw image in...
Isn't there any official way?
This is a huge problem as it is a wast of space once you have dozens containers. This means that the used space by containers can only grow so in some months you will have a lot space used by empty space. In the case above, havig 10 containers like this means...
As it seems not possible to directly use chroot for LXC storage (due to having to do it in a hacky way and apparently having problems with "su") I am using the default raw image.
The problem with this images is that once that you use space, it is never released. For example, I have a container...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.