** No longer affects: systemd (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686361
Title:
systemd does not respect nofile ulimit when running in container
To manage notifications
This bug was fixed in the package systemd - 229-4ubuntu19
---
systemd (229-4ubuntu19) xenial; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
revert, by removing ExecStart|StopPost lines, as these are not needed on
xenial and generat
Upgrading previously verified container from 229-4ubuntu18 to
229-4-ubuntu19, the container after rebuild still has observed much
higher nofile limits / not arbitrarily limited.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenia
Hello Christian, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Adjusted hard and soft nofile limits on the host to 10, launched
container and observed lower nofile limits in prlimit. Upgraded systemd
in the container from 229-4ubuntu17 to 229-4ubuntu18. Rebooted the
container and observed much higher nofile limits.
** Tags removed: verification-needed ver
Hello Christian, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu18
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
** Changed in: systemd (Ubuntu Yakkety)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686361
Title:
systemd does not respect nofile ulimit when running in containe
** Changed in: systemd (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686361
Title:
systemd does not respect nofile ulimit when running in conta
This bug was fixed in the package systemd - 232-21ubuntu4
---
systemd (232-21ubuntu4) zesty; urgency=medium
* Cherrypick upstream commit to enable system use kernel maximum limit for
RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
* debian/tests/root-
Installed zesty virtual machine, and configured to have 1048576 nofile
hard limit, verified with prlimit command.
Configured and launched lxd i386 zesty container, the prlimit had hard
limit of 65536.
Upgraded systemd in the container to 232-21ubuntu4, restarted the
container, and it now has 1048
Hello Christian, or anyone else affected,
Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
** Description changed:
+ [Impact]
+
+ * Containers cannot use maximum RLIMIT_NOFILE, because systemd sets an
+ arbitrary cap.
+
+ [Test Case]
+
+ * Start container with high RLIMIT_NOFILE (e.g. 100 000)
+ * Check that RLIMIT_NOFILE on the container is more than 65536
+
+ [Regression Potent
** Changed in: systemd (Ubuntu Zesty)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686361
Title:
systemd does not respect nofile ulimit when running in
Thank you for uploading this stable release update! To ease the SRU
review process and later package validation, could you please update the
bug description to include the relevant SRU information [1]?
[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug not
** Changed in: systemd (Ubuntu Zesty)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu Zesty)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Zesty)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu Zesty)
Milestone:
This bug was fixed in the package systemd - 233-6ubuntu1
---
systemd (233-6ubuntu1) artful; urgency=medium
Merge from Debian, existing changes:
* ubuntu: udev.postinst preserve virtio interfaces names on upgrades, on
s390x.
New udev generates stable interface names on s390x k
** Changed in: systemd (Ubuntu Artful)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686361
Title:
systemd does not respect nofile ulimit when running in c
The attachment "0001-main-improve-RLIMIT_NOFILE-handling-5795.patch"
seems to be a patch. If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a L
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status:
Would be good if we could also SRU that to Xenial as well since this is
likely what users will be using most of the time as image in their
container. Adding stgraber to this thread.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.05
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
21 matches
Mail list logo
