594
edits
Changes
Created page with "== Changes == Since {{kernel link|rhel6|042stab134.3}}: * Running Ubuntu containers with systemd 229-4ubuntu21.8 could result in application failures due to /run/lock/ permis..."
== Changes ==
Since {{kernel link|rhel6|042stab134.3}}:
* Running Ubuntu containers with systemd 229-4ubuntu21.8 could result in application failures due to /run/lock/ permission issues. (PSBM-89993)
* Running Ubuntu containers with systemd 229-4ubuntu21.9 could result in services failing to start because systemd-tmpfiles was unable to validate path due to symlinking issues. (PSBM-90038)
* Host with multiple ploop devices running on a debug kernel could crash in sysfs_addrm_start() on container stop. (PSBM-89413)
* Ploop resize could fail and lead to access beyond the end of device. (PSBM-89687)
* Ploop over Virtuozzo Storage: in rare cases, resize could lead to ploop image corruption. (PSBM-89855)
=== See also ===
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847
Since {{kernel link|rhel6|042stab134.3}}:
* Running Ubuntu containers with systemd 229-4ubuntu21.8 could result in application failures due to /run/lock/ permission issues. (PSBM-89993)
* Running Ubuntu containers with systemd 229-4ubuntu21.9 could result in services failing to start because systemd-tmpfiles was unable to validate path due to symlinking issues. (PSBM-90038)
* Host with multiple ploop devices running on a debug kernel could crash in sysfs_addrm_start() on container stop. (PSBM-89413)
* Ploop resize could fail and lead to access beyond the end of device. (PSBM-89687)
* Ploop over Virtuozzo Storage: in rare cases, resize could lead to ploop image corruption. (PSBM-89855)
=== See also ===
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847