Description of problem:
CentOS 7.5 systemd 219 within a lxd container doesn't properly set nofile open file limits. According to the below links, this was fixed in systemd 229+
I can confirm it's fixed if i manually update centos 7.5 lxd guest containers systemd version to 234 https://discuss.linuxcontainers.org/t/ulimit-nofiles-in-centos-7-5-containers-a-systemd-bug/1953
Would be great if upstream Redhat 7.x systemd backported such a fix so native CentOS 7.5 guest lxd containers would properly set nofile.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. launch a lxd guest container with centos 7.5
2. try raising nofile limit for a service and check prlimit -p PID of process - it's fixed to 65536 in systemd 219 but properly changes if updated to systemd 234
try raising nofile limit for a service and check prlimit -p PID of process - it's fixed to 65536 in systemd 219
that raising a centos 7.5 service's nofile limit should be reflected when checking service process PID limits
fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/290 -> post
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.