Remove LimitNOFILE from systemd service file

saschagrunert · saschagrunert · commit b27a733c8c80 · 2025-01-30T10:14:40.000+01:00
Explicit configuration for `LimitNOFILE` in the reference `crio.service` systemd service file is removed. CRI-O's rlimits are inherited by containers, so the daemon's `LimitNOFILE` affects `RLIMIT_NOFILE` within containers. It is recommended to use the default systemd `LimitNOFILE` configuration. Administrators on platforms running versions less than systemd 240 should explicitly configure `LimitNOFILE=1024:524288` or risk falling back to the kernel default of `4096`. Fixes: cri-o#7703 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
diff --git a/contrib/systemd/crio.service b/contrib/systemd/crio.service
@@ -17,7 +17,6 @@ ExecStart=/usr/local/bin/crio \
           $CRIO_METRICS_OPTIONS
 ExecReload=/bin/kill -s HUP $MAINPID
 TasksMax=infinity
-LimitNOFILE=1048576
 LimitNPROC=1048576
 LimitCORE=infinity
 OOMScoreAdjust=-999
