[lxc-users] Nested containers with systemd (Ubuntu 15.04)

2015-05-26 Thread Cam Cope
Can anyone confirm that container nesting works for them with Ubuntu 15.04 host + containers? So far I keep getting cgmanager errors (which I suspect are related to systemd). -Cam ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://list

Re: [lxc-users] What is the status of "stable" LXC PPA?

2016-02-24 Thread Cam Cope
Bump. Also, is the stable-1.1 PPA actually stable or not? -Cam On Sat, Feb 13, 2016 at 4:33 AM, Andrey Repin wrote: > Greetings, All! > > What is the status of > https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/stable ? > Is it supposed to contain beta builds? > > > -- > With best regards, > A

Re: [lxc-users] What is the status of "stable" LXC PPA?

2016-02-25 Thread Cam Cope
Ok, that clarification is helpful. The ppa's statuses are inconsistent with those descriptions though: - 'stable' currently contains release candidate builds of lxc - https://launchpad.net/~ubuntu-lxc states that the stable-1.0 and stable-1.1 ppa's contain "development builds" - https://launchpa

[lxc-users] Nested user namespace container fails to start

2016-03-25 Thread Cam Cope
The main error appears to be that /proc fails to mount (I bolded it below). Is there any way I can debug this further? Log: $ for cg in blkio cpu cpuacct cpuset devices freezer hugetlb memory net_cls net_prio perf_event; do sudo mkdir /sys/fs/cgroup/${cg}$(grep cpuset /proc/self/cgroup |

Re: [lxc-users] Nested user namespace container fails to start

2016-03-30 Thread Cam Cope
Fantastic, that works! The error message from that mount failure wasn't very informative. Thank you for the help. -Cam On Mon, Mar 28, 2016 at 11:14 PM, Serge Hallyn wrote: > Quoting Cam Cope (c...@dropbox.com): > > The main error appears to be that /proc fails to mount (I bol

[lxc-users] Loop devices in 16.04 containers

2016-11-10 Thread Cam Cope
Hi all, I'm trying to mount loop filesystems inside Ubuntu 16.04 containers with lxc1 v2.0.5, but there are no loop devices. It appears that systemd fails to start udev because /sys is not writable. I changed the automount config to sys:rw and restarted the container, but the loop devices still d