[pve-devel] [PATCH container v2 2/4] seccomp config: adapt to new lxc-syscalld runtime directory

[Thomas Lamprecht]

Am 30.07.25 um 14:50 schrieb Fabian Grünbichler:
>> For already running containers, a symbolic link is put into place by
>> the new version of pve-lxc-syscalld, but newly started ones should
>> always use the new socket path as soon as it is available. Only use
>> the old socket path if the old version of pve-lxc-syscalld is still
>> used. The heuristic to check this is:
>> 1. the new socket path doesn't exist
>> 2. the old socket path exists
>> 3. the old socket path is not a symbolic link
> couldn't this be solved by adding a versioned depends, instead of
> breaking the other direction which is not actually required because of
> the compat symlink?


The compat symlink only exists for the boot during which the upgrade
to the newer pve-lxc-syscalld was made, afterwards the new syscalld
really breaks older pve-container.