On St 27. srpen 2014, 20:27:51 CEST, Lennart Poettering wrote:
On Wed, 27.08.14 20:20, Václav Pavlín (vpavlin@xxxxxxxxxx) wrote:
Heya,
It's a package that fakes systemd presence in system. It's solely
intended for Docker images as we don't want systemd there (at least
as long as it takes to prepare systemd-container Michal is working
on). I made a mistake and it ended up being pulled in buildroot.
Ping me on IRC if you have more questions or comments.
So what is "systemd-container" supposed to do? And what precisely is
"fakesystemd" supposed to do? And that "mini" thing?
fakesystemd owns same directories systemd does and has set provides to
fulfill most RPM dependencies for systemd. For example you want to run
httpd in your Docker container which brings systemd, devicemapper,
kmod... in. If the base image contains fakesystemd none of these
dependencies is installed. If you really need systemd in you container
you can use following command:
yum swap -- remove fakesystemd -- install systemd systemd-libs
systemd-container (I think it's the same thing you refer to as "mini")
should remove dependencies which does not make sense in container (again
devicemapper, kmod...) and hwdb and should run as init in multi-service
containers. Well I am not sure if it ends up being really
"systemd-container" or simply "fixed" systemd. If I am not mistaken this
was second topic for last Base WG meeting which we didn't get to:) So
hopefully this week?
Vasek
This sounds all very much not thought to the end.
Can you please explain what these packages precisely do, and why they
exist?
Lennart
--
Lead Infrastructure Engineer
Developer Experience
Brno, Czech Republic
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
