Signed-off-by: S.Çağlar Onur
---
src/lxc/lxc_cgroup.c | 1 +
src/lxc/lxc_clone.c| 1 +
src/lxc/lxc_console.c | 4
src/lxc/lxc_destroy.c | 1 +
src/lxc/lxc_freeze.c | 1 +
src/lxc/lxc_info.c | 2 ++
src/lxc/lxc_snapshot.c | 1 +
src/lxc/lxc_unfreeze.c | 1 +
src/lxc/lxc_wait.c
On Thu, 2013-10-03 at 20:49 -0500, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > On Thu, 2013-10-03 at 16:58 -0500, Serge Hallyn wrote:
> > > Quoting Michael H. Warfield (m...@wittsend.com):
> > > > On Wed, 2013-10-02 at 23:39 -0500, Serge Hallyn wrote:
> > > > > Quo
Container trimming is a bad idea in general, Ubuntu since 12.04 allows
standard systems to run in containers and we've got separate code to
deal with 10.04, so let's just drop trim.
Signed-off-by: Stéphane Graber
---
templates/lxc-ubuntu.in | 96 ++---
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
Commit: 449989ac38e07080c6b951de31ccba82753058b7
https://github.com/lxc/lxc/commit/449989ac38e07080c6b951de31ccba82753058b7
Author: Michael H. Warfield
Date: 2013-10-03 (Thu, 03 Oct 2013)
Changed paths:
M templat
Quoting Michael H. Warfield (m...@wittsend.com):
> This patch reworks the Fedora template to operate in the most "distro
> agnostic" manner possible. It should even run on distros where rpm and
> yum are not present and not available or may be incompatible. It
> depends on the most basic set of s
Quoting Michael H. Warfield (m...@wittsend.com):
> On Thu, 2013-10-03 at 16:58 -0500, Serge Hallyn wrote:
> > Quoting Michael H. Warfield (m...@wittsend.com):
> > > On Wed, 2013-10-02 at 23:39 -0500, Serge Hallyn wrote:
> > > > Quoting Michael H. Warfield (m...@wittsend.com):
> > > > > +mount
On Thu, 2013-10-03 at 23:30 +0100, Christian Seiler wrote:
> Hi there,
>
> > The initial heuristic, in this case, is the existence
> > of /etc/systemd/system in the container to enable autodev. This is
> > the
> > heuristic used in the lxc-fedora template but it applicable to all
> > systemd co
Hi there,
> The initial heuristic, in this case, is the existence
> of /etc/systemd/system in the container to enable autodev. This is
> the
> heuristic used in the lxc-fedora template but it applicable to all
> systemd containers, as far as I can determine.
Just a quick note about the specific
On Thu, 2013-10-03 at 16:58 -0500, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > 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 squashfs
> >
> > > Heh, th
Quoting Michael H. Warfield (m...@wittsend.com):
> 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 squashfs
>
> > Heh, this is unfortunate - since I test things inside containers, now I
> >
My second takeaway from the Linux Plumbers conference was to do an
automatic heuristic determination when we should enable autodev
(mounting of something on /dev/ in the container at startup for things
like systemd). If autodev is not enabled when it is required (systemd)
the container can cause t
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 squashfs
> Heh, this is unfortunate - since I test things inside containers, now I
> have to face the loop device in containers issue :)
> For n
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 squashfs
> Heh, this is unfortunate - since I test things inside containers, now I
> have to face the loop device in containers issue :)
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
Commit: 025f59ab98217b7e9caf6d3ac7e910853d95f621
https://github.com/lxc/lxc/commit/025f59ab98217b7e9caf6d3ac7e910853d95f621
Author: Serge Hallyn
Date: 2013-10-03 (Thu, 03 Oct 2013)
Changed paths:
M configure.ac
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
Commit: a5a82508547320372b1d935193b85e80884e1e29
https://github.com/lxc/lxc/commit/a5a82508547320372b1d935193b85e80884e1e29
Author: Serge Hallyn
Date: 2013-10-03 (Thu, 03 Oct 2013)
Changed paths:
M src/lxc/confil
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 squashfs
>
> Heh, this is unfortunate - since I test things inside containers, now I
> have to face the loop device in containers issue :)
Yeah,
On Wed, Oct 02, 2013 at 10:30:31PM -0500, Serge Hallyn wrote:
> Some features of lxc - networking and LSM configuration for instance -
> are generally configured by the distro packages. This program
> tests the Ubuntu configuration.
>
> changelog v2:
> Switch to lxc-info -i to detect ip address
On Thu, Oct 03, 2013 at 09:32:15AM +, Purcareata Bogdan-B43198 wrote:
> Hello,
>
> I am currently running a setup with hundreds of containers starting on the
> same Linux host. Each of these containers receive a single virtual interface
> eth0 connected to a host interface using macvlan. The
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
Commit: 2aa123185e055bbe2506a6210e795e0b9375e477
https://github.com/lxc/lxc/commit/2aa123185e055bbe2506a6210e795e0b9375e477
Author: Serge Hallyn
Date: 2013-10-03 (Thu, 03 Oct 2013)
Changed paths:
M src/tests/Make
Hello,
I am currently running a setup with hundreds of containers starting on the same
Linux host. Each of these containers receive a single virtual interface eth0
connected to a host interface using macvlan. These containers only use IPv4,
but by default they receive an IPv6 address as well. T
Amir Goldstein writes:
> Excellent! let's focus the discussion on a new device driver we want
> to write
> which is namespace aware. let's call this device driver valarm-dev.
> Similarly to Android's alarm-dev, valarm-dev can be used to request
> RTC wakeup calls
> from user space and get/set RTC
On Thu, Oct 3, 2013 at 3:44 AM, Eric W. Biederman wrote:
> Amir Goldstein writes:
>
> > What we really like to see is a setns() style API that can be used to
> > add a device in the context of a namespace in either a "shared" or
> > "private" mode.
>
> I think you mean an "ip link set dev FOO net
22 matches
Mail list logo
