The packaged version of docker-systemctl-replacement contains an
upstream bug where systemctl assumes that the mtime of /proc files of
the init process is the boot time of the container. Status and PID files
with older timestamps are considered invalid and then truncated,
breaking further operations that rely on them.

Unfortunately the underlying assumption about mtime of files in /proc is
not reliable (often it works, sometimes it doesn't). As a result,
running services are unpredictably considered invalid during further
systemctl operations, notably "systemctl reload" commands.

The upstream fix notes this in comments on the new function that uses
the actual start time of the init process:

https://github.com/gdraheim/docker-systemctl-replacement/commit/2f782b85b56680f45e09f78321d14614984edbc4

Please update the package to the current upstream release, as of this
email it's 1.5.4505. I'd appreciate a backport of the fix to stable.