RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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+

https://github.com/systemd/systemd/pull/5795
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686361

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):

systemd 219


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


Actual results:

try raising nofile limit for a service and check prlimit -p PID of process - it's fixed to 65536 in systemd 219

Expected results:

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.

https://access.redhat.com/errata/RHSA-2019:2091