Quoting Serge Hallyn (serge.hal...@canonical.com): > Quoting Michael H. Warfield (m...@wittsend.com): > > On Sun, 2012-10-21 at 14:49 -0500, Serge Hallyn wrote: > > > Quoting Michael H. Warfield (m...@wittsend.com): > > > > Serge, > > > > > > > > ... > > > > > > Short of building a custom systemd, I don't know how to fix that problem > > > > and I suspect this OP is going to run into this same thing (container > > > > taking over host's console) and might explain some of what he's seeing. > > > > Several of these look like they could cause problems (like /dev/pts in > > > > there). I've really reached an impasse at getting systemd (at least > > > > Fedora 16 and 17) to work in a container without screwing up the host. > > > > Prohibiting mounts entirely in the container might work but I suspect > > > > (having read some systemd error messages) systemd is going to have some > > > > serious heartburn there. > > > > > > > > Thoughts? > > > > > > IIRC, simply having apparmor(/selinux) refuse the mount of /dev by the > > > container should work, i.e. systemd was not going to fail as a result. > > > > Hopefully, you've seen the message from Kay Sievers cc'ed to this list > > from my post to the systemd-devel list. Looks like they have a > > mechanism in place to do this... > > > > http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface > > Saw the email, haven't yet read the page, thanks.
So based on that page, what we do (set 'container=lxc') should already be sufficient. -serge ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
