2 ms·
systemd already puts each service in a separate cgroup AFAIK, so commands like cgexec aren't even needed. I suspect people are more interested in namespace sepa
by wmf 10y ago
systemd already puts each service in a separate cgroup AFAIK, so commands like cgexec aren't even needed. I suspect people are more interested in namespace separation, but recent versions of systemd can also do that [1]. I don't think systemd has image management so that's still a reason to use Docker.
[1] https://www.freedesktop.org/software/systemd/man/systemd.exec.html https://www.freedesktop.org/software/systemd/man/systemd.exe...
- gtrevorjay 10y agoIn the case of system services, it is probably acceptable (perhaps even ideal) to leave the image management up to deb, RPM, or ostree. systemd shouldn't do everything :) .
- technofiend 10y agoSystemd creates three "slices": system, user and machine. Daemons started by systemd go in system, user processes in user and virtual machines go in machine. Each process is placed in a hierarchy so you end up with system-httpd which makes it easy to assign or limit resources based on the slice. Redhat covers it extensively in their performance and tuning class.
- jvoorhis 10y agoSystemd technically does include rudimentary image management through systemd-importd and machinectl.