On Mon, Mar 17, 2014 at 09:36:42AM -0500, Serge Hallyn wrote:
>
> As I said through a third party :), please do cc: me or the lxc-devel
> list on design/code for the library.
Sure! Will do.
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
David,
One way of setting a hard limit is to use the LVM backing store and use the
--fssize option to set the size you want to allow for the container.
Cheers,
Bill
--
Bill Anderson
Cloud Sites Engineer & Mad Scientist
From: lxc-users-boun...@lists.lin
No matter what I try to do, it seems that the template that I am using does
not properly start a container using /sbin/init, and fails without error
but only the warning: "lxc_start - invalid pid for SIGCHLD". I've tried a
variety of different commands within the template in order to start the
con
Are the following lines that already exist in templates like lxc-sshd
sufficient?
lxc.mount.entry = /lib lib none ro,bind 0 0
lxc.mount.entry = /bin bin none ro,bind 0 0
lxc.mount.entry = /usr usr none ro,bind 0 0
lxc.mount.entry = /sbin sbin none ro,bind 0 0
__
So you are just asking about lxc_attach_run_fn vs.
lxc_attach_run_command? They're just both there for convenience. Use
either one.
Quoting Ranjib Dey (dey.ran...@gmail.com):
> I do have the isolation right? ruby code thats running inside attach can
> not touch host file system,has all the names
btw, there is also is another "glitch". When I run that gradle script from
console, after it finishes, I need to reset terminal, otherwise I do not
see echo from keys while typing.
At the end is some parts from host gradle script, which is responsible for
launching/managing lxc.
init function is u
Quoting Fabio Kung (fabio.k...@gmail.com):
> On Fri, Mar 14, 2014 at 08:52:46AM +1300, Gavin Grieve [DATACOM] wrote:
> > It sounds like something that should exist so if it doesn't yet, I'm quite
> > keen to put some time into it.
>
> Coincidence or not, we (at Heroku) have been exploring this ar
Quoting Haralds Ulmanis (hara...@evilezh.net):
> So, when i run from shell that gradle script - everything is fine and
> perfect. When i run from jenkins - I can't stop/kill, get info from
> containers.
> LXC is version 1.0.0 with kernel 3.13.0
> Any suggestions ?
Please show us the gradle script.
Quoting Michael H. Warfield (m...@wittsend.com):
> I'm going to make a few comments here and respond to the patch over in
> the -devel list in a bit.
>
> For openers... We should be thinking about changes like these in terms
> of all the templates. Every time this comes, the templates are
> dive
Quoting Kevin Wilson (wkev...@gmail.com):
> Michael,
> Thanks for your answer. I would appreciate if you will explicitly tell
> what should I do exactly, as I want to try it: how do I create the
> needed two loopback devices for creating a fedora container inside a
> fedora container ?
Note the ea
10 matches
Mail list logo
