This allows containers started with a configuration using the old socket path to continue calling in to the pve-lxc-syscalld, except for a brief time window after the new runtime dir is used before the postinst script runs. However, such a time window was/is already present during service restart (and thus during package upgrade), since pve-lxc-syscalld doesn't currently implement graceful reloading.
Signed-off-by: Fiona Ebner <f.eb...@proxmox.com> --- debian/postinst | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 debian/postinst diff --git a/debian/postinst b/debian/postinst new file mode 100644 index 0000000..97abc0c --- /dev/null +++ b/debian/postinst @@ -0,0 +1,19 @@ +#!/bin/sh + +set -e + +#DEBHELPER# + +case "$1" in + configure) + if test -n "$2"; then + # TODO: remove once PVE 10.0 is released + if dpkg --compare-versions "$2" 'lt' '1.3.1'; then + ln -s -f /run/pve-lxc-syscalld/lxc-syscalld.sock /run/pve/lxc-syscalld.sock + fi + fi + ;; + +esac + +exit 0 -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
