This bug is fixed for the local LXD provider scenario for 2.0 on Xenial with this commit - http://bazaar.launchpad.net/~juju- qa/ubuntu/xenial/juju/2.0.0/revision/214 - in which the juju-2.0.conf file has the settings identified and dropped into /usr/lib/sysctl.d. Unfortunately, this only addresses the case of the local LXD provider and not any other LXD usage.
For example, if you do a high density deployment using MAAS + LXD, this code only applies to the juju-2.0 packages which are installed on the machine where the juju client is run. This means that any of the other possible uses of the LXD containers within Juju are receiving the same benefit from this tweak. So to me it feels like there's a fix committed and even released, however it only partially solves tuning the system for higher density of LXD containers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
