On 18/09/13 16:43, Gary Ballantyne wrote:
I am pretty sure that XFS needs to be *initially* mounted with the quota
option --- but after rebooting I have lost the uquota.
Update:
If I create an ordinary (not lvm backed) container, then shuffle things
around so that /var/lib/lxc/vm0/rootfs
Hi All
I have a container running over a XFS logical volume, and would like to
employ user-level disk quota.
This doesn't work, but it seems like I need something like:
mount -o remount,uquota /var/lib/lxc/vm0/rootfs/
The change seems to stick:
/dev/mapper/lxc-vm0 on /var/lib/lxc/vm0/rootfs
On 14/03/13 16:31, Serge Hallyn wrote:
Looks to me like the problem is a conflict between memory cgroup and
xen:
Thanks Serge. This is the distro:
http://cloud-images.ubuntu.com/releases/raring/alpha-2/ (ami-c842608d).
And a stable version of quantal before that.
I will start by looking for
Hi All
I have an intermittent, but crippling, problem on a raring EC2 instance
(also on quantal). Its a (raring) lvm-backed container --- I use cgroups
directly (via /sys/fs) and iptables in the instance (not sure if that's
relevant at all).
Occasionally, when stopping or starting the
On 01/02/13 02:33, lxc-users-requ...@lists.sourceforge.net wrote:
On 2013-01-31 07:41, Gary Ballantyne wrote:
*# echo '64M' /sys/fs/cgroup/memory/lxc/memory.limit_in_bytes*
# cat /sys/fs/cgroup/memory/lxc/memory.limit_in_bytes (return 67108864)
Dear Gary,
what's the value of '/sys/fs/cgroup
Hello All
I understand that I can limit the RAM of a single container via
lxc.cgroup.memory.limit_in_bytes. But, is there a way to limit the total
RAM available to all containers (without limiting each individually)?
E.g., say we have 4G available. Rather than specifying a maximum number
of
On 08/12/11 19:39, Daniel Lezcano wrote:
On 12/08/2011 12:38 AM, Joseph Heck wrote:
I've been seeing a pause in the whole networking stack when starting
and stopping LXC - it seems to be somewhat intermittent, but happens
reasonably consistently the first time I start up the LXC.
I'm using
Hello All,
Is there any known means for a non-root user, who is ssh'd into a
container, to attack the host (e.g. read a file, reboot the machine ...)?
From what I have read the (potential) trouble seems to be with root
users. Is that true?
Many thanks,
Gary
On 2/6/2011 10:44 AM, Daniel Lezcano wrote:
On 02/04/2011 07:24 PM, Andre Nathan wrote:
Hello
Is it possible to have everything inside a container (including init,
getty and whatever daemons are installed) being run as a normal user?
That is, can I have a container with no root user in
On 2/3/2011 1:47 PM, Trent W. Buck wrote:
Gary Ballantyne
gary.ballant...@haulashore.com writes:
# /usr/bin/lxc-execute -n foo -f
/usr/share/doc/lxc/examples/lxc-veth.conf /bin/bash
The container fired up, and I could ping to/from the host. However, when
I left the container (with exit
Hi
Would greatly appreciate any help getting the sshd template working on
my Ubuntu 9.1 host.
I can ssh to and from the container and host when the container is
generated by:
lxc-execute -n foo2 -f /usr/share/doc/lxc/examples/lxc/lxc-veth-gb.conf
/bin/bash
Here I have slightly modified the
11 matches
Mail list logo
