1 Commits

Author	SHA1	Message	Date
Colin Walters	901917ff85	compose: Introduce a little 'libcontainer', use it for the post script ... The current motivation for this is that https://github.com/fedora-infra/fedmsg-atomic-composer started using mock --new-chroot (which uses systemd-nspawn) to run rpm-ostree, which in turn uses systemd-nspawn to run the post script. Now systemd-nspawn is not really nestable (it wants to link up journald, resolv.conf handling, etc). First, dropping nspawn and going to raw containers fixes the nesting problem. Second, we don't need all the features of systemd-nspawn. We are ok with log messages going to stdout, and we don't use networking, so no resolv.conf is needed. Third, this sets a bit of a stage for more sandboxing internally when run on real systems. I already have a prototype branch which runs librepo as an unprivileged user, that could be combined with this for even stronger security. Why not use systemd? Well...I'm still debating that. But the core problem is systemd isn't a library in the C sense - to use its sandboxing features we have to use unit files. It's harder to have a daemon that looks like a single service from a management perspective, but uses sandboxing internally.	2014-11-21 13:16:49 -05:00