[systemd-devel] [PATCH 1/1] Allow systemd to run without assigning container to machine.slice

Daniel J Walsh dwalsh at redhat.com
Fri Jan 31 05:27:29 PST 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/30/2014 07:09 PM, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Jan 30, 2014 at 04:29:14PM -0500, Dan Walsh wrote:
>> If I want to run a container as a service, it would be nice if it used
>> the service cgroup configuration
> Your patch will break the integration with machienctl, etc. Would instead
> assigning the slice with --slice be enough?
> 
> Zbyszek
> 
My goal is if I run systemd-nspawn within a systemd unit file, perhaps as a
plugin to docker, I want to allow the system administrator to just add

MemoryLimit=500m

To the unit file and have it effect the processes within the container.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLrpMEACgkQrlYvE4MpobMe5wCfaRR70wrnY2bU+SgzCFLlSeSO
CSEAn1t+TDnEkj0VeMp6HTSK/QoK2xO+
=SDyW
-----END PGP SIGNATURE-----


More information about the systemd-devel mailing list