<div dir="ltr">Thank you for sharing this Ondrej! <div> </div><div>I'm excited to hear you got nested LXC containers working for your use case. This is certainly an interesting story - as its far lighter weight than running an isolated VM.</div><div> </div><div>Cheers!</div></div><div class="gmail_extra"> <div class="gmail_quote">On Tue, Nov 18, 2014 at 4:51 AM, Ondrej Kuznik <<a href="mailto:ondrej.kuznik@credativ.co.uk" target="_blank">ondrej.kuznik@credativ.co.uk</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all, a bit of background: running Debian on a not-so-high-spec machine, the most often suggested way of running Juju (vagrant) has not been the best experience so far. The VM eats most of my RAM (the few bits not taken up by Iceweasel already) and takes ages to do the simplest of things. Yet it has worked well enough for a while, until I needed relations with the postgresql charm. That issue turns out to have been fixed since, but given that I already had to start over with a fresh VM, it was a good time to try and go native again - with LXC. According to lazyPower, noone has really tried that, or they haven't shared their experience yet. He suggested I do so, should I be successful. So here it comes. Juju a la Debian, or LXCeption ------------------------------ Ingredients: - 1 Debian Jessie (a Wheezy with backports might work as well?) - aptitude install lxc ebtables bridge-utils libvirt-bin debootstrap - a cup of <a href="https://wiki.debian.org/LXC" target="_blank">https://wiki.debian.org/LXC</a> - a pinch of <a href="https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-nesting" target="_blank">https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-nesting</a> If lxc-checkconfig approves of your machine, you can proceed to create your new container: lxc-create -n juju-host -t ubuntu-cloud -- --release trusty Then, as per the Ubuntu documentation, edit your container config (/var/lib/lxc/juju-host/config) to include: lxc.mount.auto = cgroup Sprinkle with networking of your liking and you can start the machine. Your Juju is ready to serve! As expected, it is much snappier and friendly. One gotcha is that, usually after an environment destroy, the cgroups get unmounted/somehow disabled in the container and new containers in the nest will not start. Restarting the juju host container makes that go away. Maybe that's juju being overzealous when shutting down the its machines? Can file a bug if anyone thinks it's worth investigating. Have fun, Ondrej -- Consultant credativ Ltd Suite 5, Bloxam Court Corporation Street UK office: <a href="tel:%2B44%201788%20298150" value="+441788298150">+44 1788 298150</a> Rugby Email: <a href="mailto:ondrej.kuznik@credativ.co.uk">ondrej.kuznik@credativ.co.uk</a> CV21 2DU Web: <a href="http://www.credativ.co.uk" target="_blank">http://www.credativ.co.uk</a> -- credativ Ltd is registered in England & Wales, company no. 5261743 Certified by CompTIA / AccredIT UK with the ICT Supply standard of quality for Software Product Design and Development -- Juju mailing list <a href="mailto:Juju@lists.ubuntu.com">Juju@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju</a> </blockquote></div> </div>