Why exactly is systemd-sysusers needed here anyway? Do you not have a passwd and shadow file?
On September 16, 2019 5:41:04 PM UTC, Lennart Poettering <email@example.com> wrote:
On Mo, 16.09.19 09:45, Troy Dawson (firstname.lastname@example.org) wrote:
systemd-sysusers seeks to unify user creation. It also has the
benefit of being able to create users on bootup. But, it pulls in the
entire systemd infrastructure with all it's dependencies.
containers do not need systemd to run. They are trying to be as small
as possible. But if a package in container needs to add a user, then
systemd is pulled in and that container grows by up to 60M.
Minimizing containers, both in the short term and long term, are
important to the minimization team. We have opened an issue for
Any ideas on what we recommend to users?
systemd-tmpfiles runs without PID 1 being systemd. That said,
something needs to run it. Typically that's a service manager of some
kind, since the tool is wrapped as a service. If you don't have that,
you need to call it yourself somehow differently...
That all said it's entirely sufficient to invoke the tool at container
build time, and RPM scriptlets generally do that anyway. In that case
there's no need to have it around at runtime.
Lennart Poettering, Berlin
devel mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://email@example.com
Sent from my mobile device. Please excuse my brevity.