Would it be reasonable to apply the settings that
https://github.com/lxc/lxd/blob/master/doc/production-setup.md suggests
when we add the first LXD to a machine?

What about interrogating the kernel about available resources and
refusing to add a container when it won't work? I can try adding 20
containers to a MAAS node at the moment and get no useful message and
they do start to fail.

Since Juju is running as root we could just do a sysctl key=value to set
those live and apparently changes to /etc/security/limits.conf apply to
new processes without a reboot. Preserving the sysctl over reboots isn't
difficult either.

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to