Bug#1009301: acpid: acpi.path in container generates - systemd[1]: Condition check resulted in ACPI event daemon being skipped.

[Frank Dornheim]

Package: acpi
Version: 1:2.0.32
Severity: normal

Dear Maintainer,

The package is also installed in containers for example lxc/lxd through dependencies.
Systemd deactivates acpid with the line: 'ConditionVirtualization=!container' in the section [Unit] in the file: 'acpid.service'.
The file watcher acpi.path does not have this setting, which leads to permanent errors in the log:

systemd[1]: Condition check resulted in ACPI event daemon being skipped.

Therefore, I suggest to also insert the line: 'ConditionVirtualization=!container' in the section: 'Unit' in the acpid.path file.
I tested the solution.

Thanks Frank

-- System Information:
Debian Release: bullseye
  APT prefers testing
  APT policy: (950, 'testing'), (54, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.13.0-39-generic
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages acpi depends on:
ii  libc6  2.27

acpi recommends no packages.

acpi suggests no packages.

-- no debconf information

[Nicholas Brown (Nick)]

Similar issue about this reported and worked around here:
https://github.com/OpenNebula/one/issues/5504

[Nicholas Brown (Nick)]

I’ve submitted a merge-request that should address this: https://salsa.debian.org/debian/acpid/-/merge_requests/2

[Simon Deziel]

This issue was reported in
https://discuss.linuxcontainers.org/t/odd-behavior-with-ubuntu-22-04-and-lxd-22-04-containers/14275
which lead me to report it to Ubuntu in:

https://bugs.launchpad.net/debian/+source/acpid/+bug/1977896

I had not noticed the MR on Salsa so I proposed a very similar solution
in: https://salsa.debian.org/debian/acpid/-/merge_requests/3

The only difference is that `acpid.socket` is also disabled inside
containers.