[lxc-devel] How to import/access raw devices inside the container ?

2013-10-08 Thread Gherasim Dragos
Hello, Wondering if someone can help me with this: - given a host where some raw devices are setup:  raw -qa /dev/raw/raw1:  bound to major 7, minor 1 /dev/raw/raw2:  bound to major 7, minor 2 /dev/raw/raw3:  bound to major 7, minor 3 Added the following entry in config file for the container:

Re: [lxc-devel] How to import/access raw devices inside the container ?

2013-10-08 Thread Stéphane Graber
On Tue, Oct 08, 2013 at 07:13:51AM -0700, Gherasim Dragos wrote: > Hello, > > Wondering if someone can help me with this: > > - given a host where some raw devices are setup: > >  raw -qa > /dev/raw/raw1:  bound to major 7, minor 1 > /dev/raw/raw2:  bound to major 7, minor 2 > /dev/raw/raw3:  bo

[lxc-devel] [lxc/lxc] 494fd6: lxc-ubuntu-cloud: pass --numeric-owner and -p to u...

2013-10-08 Thread GitHub
Branch: refs/heads/master Home: https://github.com/lxc/lxc Commit: 494fd6b390ecae077375e171230ce78d6784dd43 https://github.com/lxc/lxc/commit/494fd6b390ecae077375e171230ce78d6784dd43 Author: Scott Moser Date: 2013-10-08 (Tue, 08 Oct 2013) Changed paths: M templates/lxc-u

Re: [lxc-devel] [PATCH] lxc-ubuntu-cloud: pass --numeric-owner and -p to untar

2013-10-08 Thread Stéphane Graber
On Mon, Oct 07, 2013 at 08:41:23PM -0400, Scott Moser wrote: > On Mon, 7 Oct 2013, Stéphane Graber wrote: > > > On Mon, Oct 07, 2013 at 04:16:05PM -0500, Serge Hallyn wrote: > > > An example of where this can break is if you pass in sshkey to user > > > ubuntu in the container, where user ubuntu e

[lxc-devel] [lxc/lxc] 9c3bc3: lxc-ubuntu-cloud: Cope with spaces in paths

2013-10-08 Thread GitHub
Branch: refs/heads/master Home: https://github.com/lxc/lxc Commit: 9c3bc32c5789b76b8c42b75d7625377d61e052c1 https://github.com/lxc/lxc/commit/9c3bc32c5789b76b8c42b75d7625377d61e052c1 Author: Stéphane Graber Date: 2013-10-08 (Tue, 08 Oct 2013) Changed paths: M templates/l

Re: [lxc-devel] [PATCH 1/1] templates/lxc-fedora Rework for distro independence.

2013-10-08 Thread Michael H. Warfield
On Fri, 2013-10-04 at 10:56 -0500, Serge Hallyn wrote: > Quoting Michael H. Warfield (m...@wittsend.com): > > Hey Serge, > > > > On Wed, 2013-10-02 at 23:39 -0500, Serge Hallyn wrote: > > > Quoting Michael H. Warfield (m...@wittsend.com): > > > > +mount -o loop ../LiveOS/squashfs.img squashf

[lxc-devel] [lxc/lxc] ebe0ae: doc: Generate Japanese lxc-snapshot(1) man page

2013-10-08 Thread GitHub
Branch: refs/heads/master Home: https://github.com/lxc/lxc Commit: ebe0aeb19cff9539bd749107d245874774d8a371 https://github.com/lxc/lxc/commit/ebe0aeb19cff9539bd749107d245874774d8a371 Author: KATOH Yasufumi Date: 2013-10-08 (Tue, 08 Oct 2013) Changed paths: M configure.ac

[lxc-devel] [PATCH] ensure gnutls is initialized before use

2013-10-08 Thread Dwight Engen
Section 7.1.2 of the gnutls info manual states that it must be initialized with a call to gnutls_global_init before use. This fixes the syslog warning I was seeing: lxc-create: Libgcrypt warning: missing initialization - please fix the application Signed-off-by: Dwight Engen ---

[lxc-devel] [lxc/lxc] 41246c: ensure gnutls is initialized before use

2013-10-08 Thread GitHub
Branch: refs/heads/master Home: https://github.com/lxc/lxc Commit: 41246cee3bc2b4215a485dd5da33d65ae5254514 https://github.com/lxc/lxc/commit/41246cee3bc2b4215a485dd5da33d65ae5254514 Author: Dwight Engen Date: 2013-10-08 (Tue, 08 Oct 2013) Changed paths: M src/lxc/utils.

Re: [lxc-devel] [PATCH] ensure gnutls is initialized before use

2013-10-08 Thread Stéphane Graber
On Tue, Oct 08, 2013 at 12:22:57PM -0400, Dwight Engen wrote: > Section 7.1.2 of the gnutls info manual states that it must be > initialized with a call to gnutls_global_init before use. This > fixes the syslog warning I was seeing: > > lxc-create: Libgcrypt warning: missing initialization - >

[lxc-devel] Strange problem (stray mounts) with lxc-create...

2013-10-08 Thread Michael H. Warfield
Hey all, Since I'm working on testing a bunch of things, including the Fedora templates, I've been creating and destroying a LOT of containers. Every once in a while I get a failure due to failure to mount on... What I find are a large number (half dozen or more) of dangling mounts like this: /