Hello, I'm in the middle of a migration from init to systemd. I've
completed the transition of my host environment and my 6 existing
containers continue to work as expected (they all use sysvinit
internally). I've started work on a systemd container and am getting
some odd effects.
First off,
Quoting John (l...@jelmail.com):
Hello, I'm in the middle of a migration from init to systemd. I've
completed the transition of my host environment and my 6 existing
containers continue to work as expected (they all use sysvinit
internally). I've started work on a systemd container and am
Quoting Gary Ballantyne (gary.ballant...@haulashore.com):
Hi
I use lxc.aa_profile = unconfined to get the NFS client to work in a
container (precise host and container).
Is that the best approach?
If disabling apparmor works, then a custom profile should also work, and
would be your best
Hello,
I am using system LXCs on Ubuntu 11.10 (switching to 12.04 soon). I am
managing the LXCs with some home grown scripts(not via libvirtd).
If I lxc-stop a container sometimes the veth interfaces created on the
host do not go away immediately, I believe it is the same thing
described in this
On Fri, Oct 19, 2012 at 6:29 PM, Ken Caruso k...@ipl31.net wrote:
I am using system LXCs on Ubuntu 11.10 (switching to 12.04 soon). I am
managing the LXCs with some home grown scripts(not via libvirtd).
If I lxc-stop a container sometimes the veth interfaces created on the
host do not go away
On 10/19/12, Dan Kegel d...@kegel.com wrote:
On Fri, Oct 19, 2012 at 6:29 PM, Ken Caruso k...@ipl31.net wrote:
I am using system LXCs on Ubuntu 11.10 (switching to 12.04 soon). I am
managing the LXCs with some home grown scripts(not via libvirtd).
If I lxc-stop a container sometimes the veth
