Package: systemctl Version: 1.4.4181-1.1 Severity: important
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. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemctl depends on: ii python3 3.10.4-1+b1 Versions of packages systemctl recommends: ii procps 2:3.3.17-7+b1 Versions of packages systemctl suggests: ii tini 0.19.0-1
