[SOLVED] Doubts with LXC File system and LXC disk size

[superbit]

Hi,
I'm using Proxmox since 2.x version, and always has been using OpenVZ except to virtualize my only one Windows server.
Today, I installed Proxmox 4.x beta in a server. I'm new to LXC and I have some doubts:
- Is it posible to change dinamically disk size? Using Proxmox web interface it's not posible.
- How LXC stores files? When I created a LXC CT I saw in the logs that a raw file was created similar to KVM raw disk images.
In these page (https://www.stgraber.org/2013/12/21/lxc-1-0-advanced-container-usage/) I read:

Exchanging data with a container
Because containers directly share their filesystem with the host, there’s a lot of things that can be done to pass data into a container or to get stuff out.
The first obvious one is that you can access the container’s root at:
/var/lib/lxc/<container name>/rootfs/

I also read that LXC it's similar to a chroot, and I expected to be my files in /var/lib/lxc/<container name>/rootfs or in some place similar to OpenVZ private folder.
I appreciate the comments of the LXC experts.
Regards.

 

[dietmar]

- Is it posible to change dinamically disk size? Using Proxmox web interface it's not posible.

Currently not. But we will try to implement that.

- How LXC stores files? When I created a LXC CT I saw in the logs that a raw file was created similar to KVM raw disk images.

This depends on underlying storage, i.e. we use zfs subvolumes when storage is zfs based.

 

[superbit]

Currently not. But we will try to implement that.

This depends on underlying storage, i.e. we use zfs subvolumes when storage is zfs based.

Thanks Dietmar.
I'm using ext4 and LVM.
In this thread (Proxmox 4 / LXC: Chroot instead of raw images?) you recommend

Just set disk size to 0 when you create a CT

With the problem of no disk quota, but a al least I can see my CT files at /var/lib/vz/private/<ct_id>
Maybe, some people like me will apreciate the posibility of choosing another rootfs configuration for LXC different of default (loops with raw disk images) without loosing disk quota.
Thanks a lot again.