Quoting Wojciech Izykowski (wizykow...@gmail.com):
> Changes:
>
> * corrected ssh option for custom key (from -k to -i). Just see ssh
> manpage for justification.
>
> Regards,
> Wojciech
Uh, yeah, clearly noone has tried to use that :)
Thanks.
Acked-by: Serge E. Hallyn
>
> --- src/lxc/lxc-s
Quoting erkan yanar (er...@linsenraum.de):
> Ahoi Serge,
>
> On Wed, Jan 16, 2013 at 01:37:04PM -0600, Serge Hallyn wrote:
> > Hi,
> >
> > Now that the core user namespace support is in both the 3.8 kernel
> > and in the lxc staging branch, I thought it might be good to have
> > a meeting to firs
Commit 37c3dfc9 sets the wait status on only the child pid. It
intended to match the pid only once to protect against pid reuse but it
won't because the indicator was reset to 0 every time at the top of the
loop. If the child pid is reused, the wait status will be set again.
Fix by setting indicato
Hello everyone,
As you may have noticed, Daniel released LXC 0.9 on Saturday.
I've now rebased the staging branch on that and update it on github.
I'll be travelling and taking some time off over the next few days but
will nevertheless try to get the various patches currently sitting on
the mail
Hey all,
With the release of 0.9.0 I started thinking about something. We're not
signing those tarballs with PGP or even publishing MD5/SHA-1/SHA-256
checksums on them. That has been kind of a standard practice with a lot
of packages, most particularly with anything that can impact security.
the
Quoting Dwight Engen (dwight.en...@oracle.com):
> Commit 37c3dfc9 sets the wait status on only the child pid. It
> intended to match the pid only once to protect against pid reuse but it
> won't because the indicator was reset to 0 every time at the top of the
> loop. If the child pid is reused, th
Signed-off-by: Dwight Engen
---
doc/legacy/lxc-ls.sgml.in | 4 ++--
doc/lxc-execute.sgml.in | 8
doc/lxc-ps.sgml.in| 6 +++---
doc/lxc-unshare.sgml.in | 6 +++---
4 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/doc/legacy/lxc-ls.sgml.in b/doc/legacy/lxc-ls.s
Hi there,
> A draft roadmap for 1.0 can be found at:
> https://wiki.ubuntu.com/LXC/1.0-roadmap
>
> Feel free to add items to that list. We'll use the mailing-list to
> coordinate the work as usual.
I've been working on using LXC containers in a Pacemaker (Linux-HA)
environment, i.e. writing reso
Hi!
I'm on Linux 3.8 and lxc 0.9.0.
How are the user namespaces in lxc supposed to work?
I've created an opensuse instance using "lxc-create -n foo -t
/usr/share/lxc/templates/lxc-opensuse" and the added these two lines
to the config:
lxc.id_map = u 0 10 1
lxc.id_map = g 0 10 1
B
From: "S.Çağlar Onur"
Otherwise trying to start N containers in parallel gives "lxc_container: bind :
Address already in use" error.
Found while using Go bindings to create/start/stop large number of containers
in parallel so I reproduced the same using Python API to rule out possible Go
rela
Quoting Dwight Engen (dwight.en...@oracle.com):
> Signed-off-by: Dwight Engen
>
Acked-by: Serge E. Hallyn
Note i think your patch was linewrap-damaged. Could you resend
(with my ack) or post a github link?
> ---
> doc/legacy/lxc-ls.sgml.in | 4 ++--
> doc/lxc-execute.sgml.in | 8
Quoting richard -rw- weinberger (richard.weinber...@gmail.com):
> Hi!
>
> I'm on Linux 3.8 and lxc 0.9.0.
> How are the user namespaces in lxc supposed to work?
>
> I've created an opensuse instance using "lxc-create -n foo -t
> /usr/share/lxc/templates/lxc-opensuse" and the added these two lines
Quoting Christian Seiler (christ...@iwakd.de):
> Hi there,
>
> > A draft roadmap for 1.0 can be found at:
> > https://wiki.ubuntu.com/LXC/1.0-roadmap
> >
> > Feel free to add items to that list. We'll use the mailing-list to
> > coordinate the work as usual.
>
> I've been working on using LXC co
13 matches
Mail list logo
