This reverts commit 57e13a1b89.
I noticed that systemd-logind was causing problems in our
containers after a container rebuild of the f32 base image was
published about 5 days ago. I found that an issue[0] had been
filed about the problem, but that bug was reported against
Rawhide (f33). I then found that systemd had been removed from
the f32 base image after f32 was released.
This causes problems for users who expect stability out of Fedora
releases - changing the default package set means that a container
build that works one day can break the next. In our case, the
problem wasn't so much that systemd was removed, but that the unit
masks were removed. This causes some components of systemd to be
unable to function in a container, and puts a burden on users to
identify the problem.
https://pagure.io/releng/issue/9603
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1841139
It seems that systemd is required by anaconda which wants
to setup the default target. Since dnf dependencies to systemd
was dropped in [0] we need to install it explicitly.
[0] - faa199f160
Signed-off-by: Clement Verna <cverna@tutanota.com>
Those are pretty useless in containers. People want small containers and
if something extra is needed, they are going to install it. There is no
point in having python3-unbound or rpm-plugin-systemd-inhibit in there…
Closes: https://pagure.io/releng/issue/8530
Signed-off-by: Igor Gnatenko <ignatenkobrain@fedoraproject.org>
