Hi thank you for the report Antonio (and also jbarrick for the work upstream)..
Odd that inifnity doesn't do what one would think, ... Reverse (for already released distributions) I'm not so sure we should do this as it is: a) it would be a behavioral change that one might not expect e.g. relying on that limit (unlikely but possible (you can't imagine how many https://xkcd.com/1172/ there are out there) b) a drop in override by an admin can fix it if one wants the newer limit because he is affected Going forward that seems to make sense thou. Unfortunately the change - even being from April - only seems to be in v1.3.0-beta.0. We are already on 1.2.7 which released in June, but it didn't make it in there :-/ The fix itself [1] is obviously minimal and can be added. I haven't touched containerd too much yet, so I'd want to see someone elses opinion as well before doing an upload [1]: https://github.com/containerd/containerd.git ** Changed in: containerd (Ubuntu) Status: New => Triaged ** Changed in: containerd (Ubuntu) Importance: Undecided => High ** Also affects: containerd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: containerd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: containerd (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: containerd (Ubuntu Disco) Status: New => Won't Fix ** Tags added: server-next ** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839445 Title: systemd's service unit should set LimitNOFILE to 1048576 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1839445/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
