at 10:34 PM, overlay fs <overla...@gmail.com> wrote:
> Regression
> ---
> It is no longer possible to bind-mount a file into an ephemeral
> container, using the version of lxc in the lxc-daily ppa. This used
> to work; the regression was introduced some ti
Regression
---
It is no longer possible to bind-mount a file into an ephemeral
container, using the version of lxc in the lxc-daily ppa. This used
to work; the regression was introduced some time after September 15.
Details
-
If the following entry is added to the config file
hange your temporary rootfs when pivot_dir
> is
> called to /usr/lib/x86_64-linux-gnu/lxc? Standardly, I would expect
> /usr/lib/lxc/rootfs.
I'm using the default pivot_dir, AFAIK.
>
> Christian
>
> On Mon, Oct 12, 2015 at 10:34:16PM +1100, overlay fs wrote:
>> Regression
&
The bug,
'Failed to whiteout' error in Trusty with 3.19 kernel
https://lists.linuxcontainers.org/pipermail/lxc-users/2015-August/009854.html
https://bugs.launchpad.net/lxc/+bug/1486073
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490267
is present in lxc versions 1.0.7 and 1.0.8, but
On Fri Aug 14 Thomas Müller wrote:
Hi everyone,
I'm running Ubuntu trusty and recently upgraded to the new kernel (3.19).
When creating a snapshotted clone of a regular LXC container using
overlayfs, I'm now seeing the kernel error 'failed to whiteout'.
Has anyone experienced a similar
Update: the ubuntu kernel oops is the subject of bug #1465998,
https://lists.ubuntu.com/archives/kernel-team/2015-June/058689.html,
though it is described there as a panic rather than an oops. It will
be patched in the next kernel update.
___
lxc-users
This report pertains to ubuntu 14.04 host and container, with the lxc-daily ppa
and a container which includes the x11-common package.
A patch for CVE-2015-1328, overlayfs privilege escalation,
has recently been applied to the kernel,
http://www.ubuntu.com/usn/usn-2643-1/
With this patch in
These two bugs occur only for containers with a btrfs backingstore.
First, create a container with a btrfs backingstore:
$lxc-create -B btrfs -t download -n p1 -- -d ubuntu -r trusty -a amd64
Bug (1): cloned rootfs has wrong ownership:
$lxc-clone -s -o p1 -n p1_clone
$ls -ld p1_clone/rootfs
ppa:Quoting Serge Hallyn ( serge.hallyn at ubuntu.com):
I can't reproduce this. Is the 'trusty container a stock,
download-templated created container? Which lxc version
(from which ppa) are you using? What is the underlying filesystem?
Serge, thanks for looking into this.
Container
If one uses the gentoo template to create a container,
$ sudo lxc-create -t gentoo -f config -n gentoo_test
$ cat config
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
then the gentoo template configures the network connection in the
container's root
Quoting Serge Hallyn (serge.hallyn at ubuntu.com):
On Thu Feb 12, 2015 at 11:18 Fajar A. Nugraha list at fajar.net wrote:
On Thu, Feb 12, 2015 at 5:29 PM, Purcareata Bogdan b43198 at
freescale.com wrote:
On 10.02.2015 19:22, Christian Brauner wrote:
Hello,
is it currently
A wishlist for ephemeral containers.
---
lxc start c2 c3 -e Create a new local container called c3 based on local
container c2 and have it disappear on exit.
lxc file push -R source [source...] target
Wishlist: Add an option to apply a
12 matches
Mail list logo
