#1133069 systemd-standalone-sysusers: Failed to read 'basic.conf': No such file or directory #1133069
- Package:
- systemd-standalone-sysusers
- Source:
- systemd-standalone-sysusers
- Description:
- Standalone sysusers binary for use in non-systemd systems
- Submitter:
- Philipp Matthias Hahn
- Date:
- 2026-05-21 15:31:02 UTC
- Severity:
- normal
- Tags:
Dear fellow Maintainer, I'm trying to install `openssh-client` inside a Docker container, which depends on 'systemd | systemd-standalone-sysusers | systemd-sysusers'. 1. `systemd` fails to configue with … 2. `systemd-standalone-sysusers` fails with 3. With `opensysusers` providing `systemd-sysuers` it also fails with This is about 2. `basic.conf` is part of the package `systemd`: $ dpkg -S basic.conf systemd: /usr/lib/sysusers.d/basic.conf Obviously it's no a good idea to install `systemd` and `systemd-standalone-sysusers` together. Please fix systemd-standalone-sysusers.postinst. Please feel free to forward this the OpenSSH maintainers. Philipp
No, it's also in the standalone package: https://packages.debian.org/sid/amd64/systemd-standalone-sysusers/filelist does it get unpacked before failing? Do you see the basic.conf file on the filesystem?
Control: tags -1 unreproducible hand, so this looks like a problem in your specific setup # SYSTEMD_LOG_LEVEL=debug bash -x /var/lib/dpkg/info/systemd-standalone-sysusers.postinst configure + set -e + '[' configure = configure ']' + systemd-sysusers basic.conf Loaded shared library 'libselinux.so.1' via dlopen(). Loaded shared library 'libaudit.so.1' via dlopen(). Failed to connect to audit log, ignoring: Address family not supported by protocol Reading config file "/usr/lib/sysusers.d/basic.conf"… Group adm already exists. Group tty already exists. Group disk already exists. Group man already exists. Group kmem already exists. Group dialout already exists. Group fax already exists. Group voice already exists. Group cdrom already exists. Group floppy already exists. Group tape already exists. Group sudo already exists. Group audio already exists. Group dip already exists. Group operator already exists. Group src already exists. Group shadow already exists. Group utmp already exists. Group video already exists. Group sasl already exists. Group plugdev already exists. Group staff already exists. Group games already exists. Group users already exists. Group nogroup already exists. Group lpadmin already exists. Group root already exists. User root already exists. Group daemon already exists. User daemon already exists. Group bin already exists. User bin already exists. Group sys already exists. User sys already exists. User sync already exists. Group games already exists. User games already exists. Group man already exists. User man already exists. Group lp already exists. User lp already exists. Group mail already exists. User mail already exists. Group news already exists. User news already exists. Group uucp already exists. User uucp already exists. Group proxy already exists. User proxy already exists. Group www-data already exists. User www-data already exists. Group backup already exists. User backup already exists. Group list already exists. User list already exists. Group irc already exists. User irc already exists. User _apt already exists. User nobody already exists. Notify message sent to '/run/host/notify': "EXIT_STATUS=0"
Hello Luca, my (now modified) `Dockerfile` is just this: For reference the base image is library/debian:sid-slim@sha256:79f776bfe715648269ab38476c7962ea2ccae5d5576b23a34613515ba7273d29 Adding the SYSTEMD_LOG_… settings finally made the problem visible: … … … src/basic/stat-util.c:380: statx() does not support 'STATX_MNT_ID' mask (running on an old kernel?) … src/basic/conf-files.c:976: Failed to read 'basic.conf': No such file or directory Without the SYSTEMD_LOG_… settings the error message is not visible on STDERR and `systemd-sysusers basic.conf` fails with that *wrong* error message, which makes the underlying problem hard to identify. Good for you this is already mention in the NEW file: Background: I'm building a Docker image with latest `cppcheck` from Debian Sid using a GitLab pipeline. I have no control over the docker host which is used to build the image, so I cannot control the kernel version. Obviously it's some very old 5.4.0-216-generic #236-Ubuntu focal (20.04) :-( I'll ask our IT department if an update is possible. Maybe `systemd` could print a better error message in that case hinting at the too old kernel version instead of starting a hunt for a missing `base.conf` 🤔 Thank you for your work Philipp
Hello, I just hit this with Debian testing in a WSL1 container (a bit of an odd combo I know). http://snapshot.debian.org/archive/debian/20260518T000000Z and Image Digest: docker.io/library/debian@sha256:942aae6c16e617a949763462ec3b6b5d65e60d90e4cae762bc1bce0522d26fa2 For my workaround installing `opensysusers` was the way to go and manually doing `groupadd -r _ssh` to get things working. Logs as follows: Thanks, Imran