Quoting Xavier Gendre (gendre.rei...@gmail.com):
> Le 15/06/2015 17:17, Serge Hallyn a écrit :
> >Quoting Xavier Gendre (gendre.rei...@gmail.com):
> >>Hi,
> >>
> >>i wanted to run a container in an unpriviledged container and i am
> >>glad to succes in doing it. The point is that i am not sure if w
Hm, so does adding a "sleep 1m" in /etc/init/lxc.conf right before
the call to lxc-autostart help?
Quoting Alan Hoffmeister (alanhoffmeis...@gmail.com):
> yes, exactly.
>
>
> --
> Alan Hoffmeister
> https://twitter.com/alan_hoff
> https://github.com/alanhoff
> https://keybase.io/alanhoff
>
> 20
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 crea
Quoting Akshay Karle (akshay.a.ka...@gmail.com):
> Hey,
>
> I'm running docker inside the unprivileged lxc container. So when I checked
> /proc/self/uid_map inside the lxc container it shows a different range of
> uids:
> 0 10 65536
> which I think are the default values, rig
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?
Quoting overlay fs (overla...@gmail.com):
> This report pertains to ubuntu 14.04 host and container, with the lxc
Hey,
I'm running docker inside the unprivileged lxc container. So when I checked
/proc/self/uid_map inside the lxc container it shows a different range of
uids:
0 10 65536
which I think are the default values, right? So are there no other ways to
detect what all devices can b
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 place
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 p1/r
Am 2015-06-15 17:33, schrieb Serge Hallyn:
Quoting Matthias Leopold (matth...@leopold.priv.at):
Hi,
i'm very new to lxc and btrfs. i'm just playing around and can't use
lxc-snapshot like it's being described.
error looks like this
root@debian:~# lxc-snapshot -n c001
lxc_container: failed gett
