On 05/27/2014 02:58 PM, Seth Forshee wrote:
>
> The patches implement a psuedo filesystem for loop devices, which will
> allow use of loop devices in containters using standard utilities. Under
> normal use a loopfs mount will initially contain a single device node
> for loop-control which can be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have the following proposition.
Number of currently running processes is accounted at the root user namespace.
The problem I'm facing is that multiple
containers in different user namespaces share the process counters.
So if containerX run
On Wed, May 28, 2014 at 03:58:07PM +, Serge Hallyn wrote:
> Quoting Dwight Engen (dwight.en...@oracle.com):
> > On Wed, 28 May 2014 14:51:55 +
> > Serge Hallyn wrote:
> >
> > > Quoting Dwight Engen (dwight.en...@oracle.com):
> > > > Currently, a user has to read kernel/Documentation/cgrou
Hi Serge,
On Tue, May 27, 2014 at 5:24 PM, Serge Hallyn wrote:
> Originally we kept snapshots under /var/lib/lxcsnaps. If a
> separate btrfs is mounted at /var/lib/lxc, then we can't
> make btrfs snapshots under /var/lib/lxcsnaps.
>
> This patch moves the default directory to /var/lib/lxc/c/snap
"Serge E. Hallyn" writes:
>> I was aware of FUSE but hadn't ever looked at it much. Looking at it
>> now, this isn't going to satisfy any of the use cases I know about,
>> which are wanting to use filesystems supported in-kernel (isofs, ext*).
>> I don't see that any of these have a FUSE implement
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
Commit: c83462d56db1c8ed4cf4dc575aead06d92b7a341
https://github.com/lxc/lxc/commit/c83462d56db1c8ed4cf4dc575aead06d92b7a341
Author: bartekplus
Date: 2014-05-28 (Wed, 28 May 2014)
Changed paths:
M src/lxc/confile.
On Wed, 2014-05-28 at 09:10 -0700, Andy Lutomirski wrote:
> On Wed, May 28, 2014 at 12:32 AM, Seth Forshee
> wrote:
> > On Tue, May 27, 2014 at 03:19:15PM -0700, Andy Lutomirski wrote:
> >> On Tue, May 27, 2014 at 2:58 PM, Seth Forshee
> >> wrote:
> >> > I'm posting these patches in response to t
On Wed, May 28, 2014 at 12:32 AM, Seth Forshee
wrote:
> On Tue, May 27, 2014 at 03:19:15PM -0700, Andy Lutomirski wrote:
>> On Tue, May 27, 2014 at 2:58 PM, Seth Forshee
>> wrote:
>> > I'm posting these patches in response to the ongoing discussion of loop
>> > devices in containers at [1].
>> >
Quoting Dwight Engen (dwight.en...@oracle.com):
> On Wed, 28 May 2014 14:51:55 +
> Serge Hallyn wrote:
>
> > Quoting Dwight Engen (dwight.en...@oracle.com):
> > > Currently, a user has to read kernel/Documentation/cgroups/* to
> > > know what is available and then apply these using lxc-cgroup
On Wed, 28 May 2014 14:51:55 +
Serge Hallyn wrote:
> Quoting Dwight Engen (dwight.en...@oracle.com):
> > Currently, a user has to read kernel/Documentation/cgroups/* to
> > know what is available and then apply these using lxc-cgroups to
> > set runtime limits, or hand edit the configuration
Quoting Dwight Engen (dwight.en...@oracle.com):
> Currently, a user has to read kernel/Documentation/cgroups/* to know what
> is available and then apply these using lxc-cgroups to set runtime limits,
> or hand edit the configuration file after creating a container to set them
> permanently.
>
> T
Quoting James Bottomley (james.bottom...@hansenpartnership.com):
> On Mon, 2014-05-26 at 00:24 +0200, Serge E. Hallyn wrote:
> > Quoting James Bottomley (james.bottom...@hansenpartnership.com):
> > > On Sat, 2014-05-24 at 22:25 +, Serge Hallyn wrote:
> > > > Quoting James Bottomley (james.botto
Quoting Seth Forshee (seth.fors...@canonical.com):
> On Fri, May 23, 2014 at 03:23:50PM -0700, Eric W. Biederman wrote:
> > Serge Hallyn writes:
> >
> > > Quoting Eric W. Biederman (ebied...@xmission.com):
> > >>
> > >>
> > >> >> Ultimately the technical challenge is how do we create a block de
On Fri, May 23, 2014 at 03:23:50PM -0700, Eric W. Biederman wrote:
> Serge Hallyn writes:
>
> > Quoting Eric W. Biederman (ebied...@xmission.com):
> >>
> >>
> >> >> Ultimately the technical challenge is how do we create a block device
> >> >> that is safe for a user who does not have any capabi
On Tue, May 27, 2014 at 03:56:53PM -0700, Randy Dunlap wrote:
> On 05/27/2014 02:58 PM, Seth Forshee wrote:
> > Add limited capability for use of loop devices in containers via
> > a loopfs psuedo fs. When mounted this filesystem will contain
> > only a loop-control device node. This can be used to
On Tue, May 27, 2014 at 03:19:15PM -0700, Andy Lutomirski wrote:
> On Tue, May 27, 2014 at 2:58 PM, Seth Forshee
> wrote:
> > I'm posting these patches in response to the ongoing discussion of loop
> > devices in containers at [1].
> >
> > The patches implement a psuedo filesystem for loop devices
On Mon, 2014-05-26 at 00:24 +0200, Serge E. Hallyn wrote:
> Quoting James Bottomley (james.bottom...@hansenpartnership.com):
> > On Sat, 2014-05-24 at 22:25 +, Serge Hallyn wrote:
> > > Quoting James Bottomley (james.bottom...@hansenpartnership.com):
> > > > On Fri, 2014-05-23 at 11:20 +0300, M
17 matches
Mail list logo
