What do you mean by "not using real device"? The real lvm device is
mounted into the container. However actually offering the device node
into the container would not be a safe default. In particular, it
allows the container admin to write nonsense onto the device node,
feeding garbage into the in-kernel filesystem driver, and most likely
either DOS or gain privilege on the host.
If root in the container is trusted, then it should be possible to work
this out, but frankly noone seems to have wanted this yet.
There is probably an easier way to achieve what you want. For instance,
setting up quotas on the host for the container users/filesystems.
** Changed in: lxc (Ubuntu)
Importance: Low => Wishlist
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1515615
Title:
Disk quotas don't work in LXC containers
Status in lxc package in Ubuntu:
Triaged
Bug description:
I'm trying to enable disk quotas in LXC container by adding option to its
config:
lxc.rootfs.options = usrquota
After booting the container I'm trying to initialize quotas but
getting the following error:
r...@test.lxc:~# quotacheck -gum /
quotacheck: Cannot stat() mounted device /dev/lxc/test: No such file or
directory
quotacheck: Mountpoint (or device) / not found or has no quota enabled.
quotacheck: Cannot find filesystem to check or filesystem not mounted with
quota option.
Host OS: Ubuntu 15.04
Guest OS: Ubuntu 14.04.3 LTS
lxc 1.1.2-0ubuntu3.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515615/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
