Setting them as global defaults is a good idea! In the meanwhile, have a read of this bug we filed for exactly this about a year ago:
https://bugs.launchpad.net/juju-core/+bug/1379882 Maybe the LXD provider Marco mentioned will make this moot. If so, just keep that bug on your radar and invalidate it if needed. Cheers, - Daniel On Wed, Oct 14, 2015 at 8:30 PM, Marco Ceppi <[email protected]> wrote: > For the time being you can add these entries to the lxc container defaults, > which should be in `/etc/lxc/default.conf` and new containers launched will > have those updated values. Going forward, we're working on a LXD provider > for Juju - part of that work will enable nesting of containers by default. > The local provider has always been a "work around" for developers, with the > LXD machine container hypervisor you'll be able to emulate deployments like > you do on clouds (with LXC nested) on your laptop. > > Marco > > On Wed, Oct 14, 2015 at 7:36 PM Frederico Araujo <[email protected]> wrote: >> >> For now, I'm just editing the configuration of the lxc container from >> which juju clone new lxc instances, so that all new machines allow nested >> containers. >> It would be nice if we could override container configurations during >> deployment, though :) >> >> On Wed, Oct 14, 2015 at 6:13 PM, Frederico Araujo <[email protected]> >> wrote: >>> >>> Hi, >>> >>> I wrote a charm for an application I developed which deploys some lxc >>> containers. I wanted to test it in my local environment (bootstrapped with >>> juju-quickstart), but I couldn't find a way to configure juju to >>> automatically create containers with specific settings---in my case, >>> allowing for nested lxc containers. I need to somehow change the >>> configuration fo the parent lxc container created by juju during deployment >>> of the charm to add these two lines: >>> >>> lxc.mount.auto = cgroup >>> lxc.aa_profile = lxc-container-default-with-nesting >>> >>> After manually adding these lines to the parent container created by >>> juju, the internal containers work. The problem of adding them manually is >>> that juju won't be able to start the internal containers automatically >>> during juju deploy. >>> >>> Any ideas? >>> >>> Thanks, >>> Fred >> >> >> -- >> Juju mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
