I gave it a try with the test kernel shared by Dimitri.
1. Launch a jammy(kernel version: 5.15.0-25-generic) based LXD VM locally
2. Disable the security boot.
3. Install the test kernels (version: 5.15.0-26-generic)
4. Reboot the VM
5. Install the latest lxd snap(5.0.0-e478009) from the store
6.
** Description changed:
[Impact]
- * Allow setting lower pid_max on per namespace basis, to support legacy
+ * Allow setting lower pid_max on per namespace basis, to support legacy
workloads on modern hosts.
- * Cherrypick patches from
+ * Cherrypick patches from
https://gitlab.com
Entering mount & pid namespace, as initial namespace root does not let
me set pid_max inside the container.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968886
Title:
Provide pid_max
Changing pid_max on the host to a lower value, kept high value in the
container.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968886
Title:
Provide pid_max namespace support
Status i
4 matches
Mail list logo
