Oleg Vinichenko Posted October 11, 2018 Report Share Posted October 11, 2018 pam-1.3.0-r3 update provides better values for maximum open files in /etc/security/limits.conf. This is good values on modern systems. However it was found that pam_limits.so that actually setting the limits has bug that occurs in LXD containers, which results in incorrect limits handle. As a consequence, after reboot of containers SSH connection can be terminated. We will fix pam_limits.so soon, so that it will correctly handle limits inside containers. In the mean time, DO NOT UPDATE /etc/security/limits.conf inside LXD containers. LXD containers should have NO limits set in /etc/security/limits.conf until we have fixed the upstream bug. Link to comment Share on other sites More sharing options...
palica Posted October 13, 2018 Report Share Posted October 13, 2018 Why not add -r3 masked, so the ones that need the change can unmask it and others that don't care won't be affected (esp. in containers)? Link to comment Share on other sites More sharing options...
Recommended Posts