To clarify, you are saying that this issue occurs any time you run `systemctl daemon-reexec`, right? It is not isolated to that command being run during a package upgrade?
I am not familiar with OpenVZ, but I am confused by the kernel situation. Are you saying that the containers which are running Ubuntu (and where you are seeing this problem) are running different kernels than the host?
Like I said, I am not familiar with OpenVZ, but from my understanding of other container environments like LXD, I would expect the containers to share the host's kerenl (and therefore report the same uname -a output).
To clarify, you are saying that this issue occurs any time you run `systemctl daemon-reexec`, right? It is not isolated to that command being run during a package upgrade?
I am not familiar with OpenVZ, but I am confused by the kernel situation. Are you saying that the containers which are running Ubuntu (and where you are seeing this problem) are running different kernels than the host?
Like I said, I am not familiar with OpenVZ, but from my understanding of other container environments like LXD, I would expect the containers to share the host's kerenl (and therefore report the same uname -a output).