commit | 645801e68786f36018ddba38ef9fd22b6fc6188f | [log] [tgz] |
---|---|---|
author | ChromeOS Developer <teratipally@google.com> | Thu Aug 26 21:17:07 2021 +0000 |
committer | Varsha Teratipally <teratipally@google.com> | Fri Aug 27 21:37:31 2021 +0000 |
tree | 66d86b1b06fd301337354afc0f12bbb47114e996 | |
parent | 87c7327335b3a41fc3b7c06f628a049bae3b7aa4 [diff] |
project-lakitu: disable file limits to max The change in containerd is because of performance regression with accounting overhead and where as the systemd upstream pushed those limit to be able use kernel memcg. Docker also uses INFINITY as the limit https://github.com/moby/moby/blob/master/contrib/init/systemd/docker.service#L31. Limits are ignored in ExecPreStart - another concern if set the LIMITNOFILE in dockerd and containerd Disabling the file limits in systemd BUG=b/195443901 TEST=manual verification RELEASE_NOTE=None Change-Id: I42a0d674b863ebd04d02a5d90e8b93cd97d38ce8 Reviewed-on: https://cos-review.googlesource.com/c/cos/overlays/board-overlays/+/21911 Tested-by: Cusky Presubmit Bot <presubmit@cos-infra-prod.iam.gserviceaccount.com> Reviewed-by: Vaibhav Rustagi <vaibhavrustagi@google.com> Reviewed-by: Robert Kolchmeyer <rkolchmeyer@google.com>
diff --git a/project-lakitu/sys-apps/systemd/systemd-248.6.ebuild b/project-lakitu/sys-apps/systemd/systemd-248.6.ebuild index 7a60570..2372781 100644 --- a/project-lakitu/sys-apps/systemd/systemd-248.6.ebuild +++ b/project-lakitu/sys-apps/systemd/systemd-248.6.ebuild
@@ -394,6 +394,8 @@ -Dsysusers=false -Dtimesyncd=false -Dvconsole=false + -Dbump-proc-sys-fs-file-max=false + -Dbump-proc-sys-fs-nr-open=false )