this patchset updates lxc to 4.0.4
tested on my system and a virtual ceph-cluster (for ha and migration tests),
created some backups of containers. - everything seems to work fine.
Stoiko Ivanov (2):
update upstream to 4.0.4 and rebase patches
bump version to 4.0.4-1
debian/changelog | 6 +++++
...ning-lxc-monitord-as-a-system-daemon.patch | 4 +--
...roup.dir.-monitor-container-containe.patch | 8 +++---
....container.namespace-lxc.cgroup.cont.patch | 2 +-
...dd-and-document-cgroup_advanced_isol.patch | 14 +++++-----
...up.dir.-monitor-container-container..patch | 2 +-
...09-cgroups-adhere-to-boolean-return.patch} | 4 +--
...the-right-path-in-get_cgroup-command.patch | 25 ------------------
...rvice-start-after-a-potential-syslo.patch} | 0
...ig-deny-rw-mounting-of-sys-and-proc.patch} | 0
...PVE-Config-attach-always-use-getent.patch} | 8 +++---
...apparmor-Allow-ro-remount-of-boot_id.patch | 26 -------------------
debian/patches/series | 10 +++----
lxc | 2 +-
14 files changed, 32 insertions(+), 79 deletions(-)
rename debian/patches/pve/{0010-cgroups-adhere-to-boolean-return.patch =>
0009-cgroups-adhere-to-boolean-return.patch} (90%)
delete mode 100644
debian/patches/pve/0009-get-the-right-path-in-get_cgroup-command.patch
rename
debian/patches/pve/{0011-PVE-Config-lxc.service-start-after-a-potential-syslo.patch
=> 0010-PVE-Config-lxc.service-start-after-a-potential-syslo.patch} (100%)
rename
debian/patches/pve/{0012-PVE-Config-deny-rw-mounting-of-sys-and-proc.patch =>
0011-PVE-Config-deny-rw-mounting-of-sys-and-proc.patch} (100%)
rename debian/patches/pve/{0013-PVE-Config-attach-always-use-getent.patch =>
0012-PVE-Config-attach-always-use-getent.patch} (89%)
delete mode 100644
debian/patches/pve/0014-apparmor-Allow-ro-remount-of-boot_id.patch
--
2.20.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
