[lxc-users] Problems with user sessions inside a Ubuntu Desktop Container

2016-01-21 Thread Jäkel , Guido
Dear all, this is my 2nd try to get an "Ubuntu Desktop" container running on a hosting server using "Gentoo" at home. The server is used as a router, media server, audio player. It is used and administrated "headless" via ssh. But it's hardware is a vanilla PC and now it also should be usable

[lxc-users] FollowUp: Problems with user sessions inside a Ubuntu Desktop Container

2016-01-21 Thread Jäkel , Guido
In addition, it might be helpful for you to get an outline of the current running processes and daemons inside the "Desktop Container": root@delly ~ # ps faux | cut -c 66- [...] lxc-start -n celly -l DEBUG -L /var/log/lxc/celly.out \_ /sbin/init \_ up

Re: [lxc-users] lxc-autostart, systemd and cgroups

2016-01-21 Thread Fajar A. Nugraha
On Thu, Jan 21, 2016 at 8:11 AM, Carlos Alberto Lopez Perez < clo...@igalia.com> wrote: > On 20/01/16 23:57, Fajar A. Nugraha wrote: > > Yep. I don't know when it was fixed, but my test system works fine. # pstree -pa > > systemd,1 > │ > ├─ [ unrelated process ] > | > ├─lxc-autostar

Re: [lxc-users] LXC not responsive after update

2016-01-21 Thread Viktor Trojanovic
On 20.01.2016 23:50, Fajar A. Nugraha wrote: On Thu, Jan 21, 2016 at 5:49 AM, Fajar A. Nugraha > wrote: On Thu, Jan 21, 2016 at 5:23 AM, Viktor Trojanovic mailto:vik...@troja.ch>> wrote: I just did a system upgrade on my Arch System which included

Re: [lxc-users] Unsupervised containers

2016-01-21 Thread Stewart Brodie
wrote: > > > > Right now, there is one lxc-start process per container running (that > > has renamed itself in lxc 1.1.4 to [lxc-monitor]) to act as the > > interface to the container for various LXC tools. > > > > I'd like that process to exit once the container is up and running. I do > > not w

[lxc-users] trying to create/install mate-desktop into unprivileged LXC container fails

2016-01-21 Thread brian mullan
My host is Ubuntu 15.10 with LXD/LXC installed. LXC is v 0.27 I have a script that creates a Privileged LXC container and attempts to create/install mate-desktop into *Privileged* LXC container... this all works fine! If I modify the line in the script to create an Unprivileged LXC container t

Re: [lxc-users] trying to create/install mate-desktop into unprivileged LXC container fails

2016-01-21 Thread brian mullan
I should mention that I installed LXD/LXC using the ppa: *add-apt-repository ppa:ubuntu-lxc/lxd-stable* I know I mentioned that I was using LXC v 0.27 in the question I asked although *I know I actually* have LXD v0.27 and LXC is actually v 1.15. However I just ran the following and that's what

Re: [lxc-users] LXC not responsive after update

2016-01-21 Thread Bostjan Skufca
strace command is your friend. b. On 21 January 2016 at 12:12, Viktor Trojanovic wrote: > > > On 20.01.2016 23:50, Fajar A. Nugraha wrote: > > On Thu, Jan 21, 2016 at 5:49 AM, Fajar A. Nugraha < > l...@fajar.net> wrote: > >> On Thu, Jan 21, 2016 at 5:23 AM, Viktor Trojanovic >> wrote: >> >>>

Re: [lxc-users] trying to create/install mate-desktop into unprivileged LXC container fails

2016-01-21 Thread Serge Hallyn
Quoting brian mullan (bmullan.m...@gmail.com): > My host is Ubuntu 15.10 with LXD/LXC installed. LXC is v 0.27 > > I have a script that creates a Privileged LXC container and attempts to > create/install mate-desktop into *Privileged* LXC container... this all > works fine! > > If I modify the

Re: [lxc-users] LXC not responsive after update

2016-01-21 Thread Viktor Trojanovic
Hi Bostjan, Here is my strace to "lxc-ls -f". It looks the same with the other commands, at least the last line is identical. # strace -eopen lxc-ls -f open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib/libpython3.5m.so.1.0", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib/libpthread.so.0", O

Re: [lxc-users] LXC not responsive after update

2016-01-21 Thread Bostjan Skufca
Do not add -eopen argument, as it limits your view. Do this: - strace -f -tt -r lxc-ls -f And while strace is running and your program is hanging, find its pid (of lxc-ls, not strace) and run lsof -p PID (if it will be hanging on socket, this will give you a hint what that socket is). b. On 21