We want to stop systemd from being added to docker images, because of rpm requiring systemctl.

Adam Jackson ajax at redhat.com
Mon Apr 28 22:44:39 UTC 2014

On Mon, 2014-04-28 at 17:01 -0400, Daniel J Walsh wrote:
> The problem  is lots of services require systemd because they ship a
> unit file and want systemctl reload to happen.  Systemd then triggers a
> require for udev and kmod, which docker containers do not need.
> rpm -q --whatrequires systemd| wc -l
> 151
> On rawhide I see 151 packages on my system which require systemd.
> We have a couple of options we could add a package called fakesystemd
> which provides a /usr/bin/systemctl that does nothing and does a
> provides systemd in the specfile.  Then if the user wanted to install
> systemd into a container it would need to obsolete the fakesystemd package.
> Or we could break out /usr/bin/systemctl into its own package and have
> it be smart enough to do nothing if systemd did not exist.

Or you could just rpm -e systemd once you've done the initial rpm
install, since it's just a Requires(post) and not a permanent Requires?

- ajax

More information about the devel mailing list