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

[Daniel J Walsh]

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

On 01/31/2014 10:45 AM, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Jan 31, 2014 at 10:00:12AM -0500, Daniel J Walsh wrote:
>> My plan is not to have the user no they are running systemd-nspawn
>> 
>> Imaging the user is creating a httpd container unit file using docker, 
>> described in this document.
>> 
>> http://welldefinedbehaviour.wordpress.com/2014/01/30/adventures-with-containerization-fedora-docker-and-httpd/
>>
>>
>>
>> 
[Unit]
>> Description=example.com Container After=docker.service
>> 
>> [Service] Type=simple ExecStart=/usr/bin/docker run -v
>> /srv/example.com:/srv httpd-test1 Restart=on-failure
>> 
>> 
>> Currently docker uses lxc tools under the covers to launch the container,
>> we want to add a plugin to use systemd-nspawn.
>> 
>> docker -> systemd-nspawn -> container
>> 
>> But we want the docker, systemd-nspawn and the container all affected by
>> any Cgroup entries in the unit file.  So I want the container to run as a
>> service slice not a machine slice.
> And if you specify --slice=system-<something>.slice, doesn't this do the
> job?
> 
> Zbyszek
> 

How would the docker command know what slice to assign it to?  Why not just
eliminate systemd-nspawn doing anything with slices if I pass the service flag
or some other flag.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLrxnoACgkQrlYvE4MpobO1mgCglDP9B5DadqucUEyxAgSeBVYf
G3sAoIBuzpooNd5K+cBQ8ks22pxp6az5
=qw4r
-----END PGP SIGNATURE-----