On Wed, 2014-06-04 at 17:41 -0400, Stéphane Graber wrote:
> On Wed, Jun 04, 2014 at 05:32:37PM -0400, Michael H. Warfield wrote:
> > On Wed, 2014-04-30 at 15:47 -0400, Stéphane Graber wrote:
> > > Hello,
> >
> > > I intend to release 1.0.4 next week and am currently going through all
> > > the com
On Wed, Jun 04, 2014 at 05:32:37PM -0400, Michael H. Warfield wrote:
> On Wed, 2014-04-30 at 15:47 -0400, Stéphane Graber wrote:
> > Hello,
>
> > I intend to release 1.0.4 next week and am currently going through all
> > the commits in master which should be included in the bugfix release.
>
> "N
On Wed, 2014-04-30 at 15:47 -0400, Stéphane Graber wrote:
> Hello,
> I intend to release 1.0.4 next week and am currently going through all
> the commits in master which should be included in the bugfix release.
"Next week" came and passed but we've all been busy (especially you).
Any time frame
Branch: refs/heads/stable-1.0
Home: https://github.com/lxc/lxc
Commit: 3fd1eb05066b8a881a99f59af9f3f0f400188da7
https://github.com/lxc/lxc/commit/3fd1eb05066b8a881a99f59af9f3f0f400188da7
Author: Stéphane Graber
Date: 2014-06-04 (Wed, 04 Jun 2014)
Changed paths:
M src/lxc
Branch: refs/heads/master
Home: https://github.com/lxc/lxc
Commit: 307ab05d0f0d62dfd3fc6bd965c317e8ca02fb1e
https://github.com/lxc/lxc/commit/307ab05d0f0d62dfd3fc6bd965c317e8ca02fb1e
Author: Stéphane Graber
Date: 2014-06-04 (Wed, 04 Jun 2014)
Changed paths:
M src/lxc/com
Quoting Stéphane Graber (stgra...@ubuntu.com):
> This hides some of the confusing "command X failed to receive response"
> why are usually caused by another more understandable error.
>
> On failure to start() from lxc-start, a new error message is displayed,
> suggesting the user sets logfile and
This hides some of the confusing "command X failed to receive response"
why are usually caused by another more understandable error.
On failure to start() from lxc-start, a new error message is displayed,
suggesting the user sets logfile and loglevel and if using -d, restarts
the container in the
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/snaps.
> If /va
Branch: refs/heads/stable-1.0
Home: https://github.com/lxc/lxc
Commit: 830105a08e044eac73f8accb3636ea51aabfed44
https://github.com/lxc/lxc/commit/830105a08e044eac73f8accb3636ea51aabfed44
Author: Serge Hallyn
Date: 2014-06-04 (Wed, 04 Jun 2014)
Changed paths:
M src/lxc/bd
On Wed, Jun 04, 2014 at 10:16:10AM -0500, Serge Hallyn wrote:
> It is not possible to mount a block device from a non-init user namespace.
> Therefore if root on the host is starting a container with a uid
> mapping, and the rootfs is a block device, then mount the rootfs before
> we spawn the cont
It is not possible to mount a block device from a non-init user namespace.
Therefore if root on the host is starting a container with a uid
mapping, and the rootfs is a block device, then mount the rootfs before
we spawn the container init task.
This addresses https://github.com/lxc/lxc/issues/221
Branch: refs/heads/stable-1.0
Home: https://github.com/lxc/lxc
Commit: 70f3eb4e850daa87ab50e3515380520ed44363d3
https://github.com/lxc/lxc/commit/70f3eb4e850daa87ab50e3515380520ed44363d3
Author: S.Çağlar Onur
Date: 2014-06-04 (Wed, 04 Jun 2014)
Changed paths:
M src/lxc/l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/03/2014 08:54 PM, Eric W. Biederman wrote:
> Serge Hallyn writes:
>
>> Quoting Pavel Emelyanov (xe...@parallels.com):
>>> On 05/29/2014 07:32 PM, Serge Hallyn wrote:
Quoting Marian Marinov (m...@1h.com):
> We are not using NFS. We are
13 matches
Mail list logo
