Re: [atomic-devel] Systemd, containers, and pid=host

[Clayton Coleman <ccoleman redhat com>]

Oops, I meant "outside of containers so that people can easily move simple apps into containers"


> On Mar 11, 2015, at 4:13 PM, Clayton Coleman <ccoleman redhat com> wrote:
> 
> Having systemd be able to run as a supervisors replacement in user space would be a killer feature for containers.
> 
> 
>> On Mar 11, 2015, at 4:11 PM, Lars Kellogg-Stedman <lars redhat com> wrote:
>> 
>> Is it possible to design a container that utilizes systemd *and* that
>> will run fine either with or without --pid=host?  As far as I can
>> tell, at the moment the answer is "no": if you expect to run in the
>> host pid namespace, you only get (a) a single process or (b) you use
>> some suboptimal process supervisor like "supervisor"...
>> 
>> ...but I am looking for a second opinion.
>> 
>> As for why you would want to do this, the ability to "yum install foo;
>> systemctl enable foo" is attractive, and I really like journald as a
>> solution to application logging.
>> 
>> Thanks,
>> 
>> -- 
>> Lars Kellogg-Stedman <lars redhat com> | larsks @ {freenode,twitter,github}
>> Cloud Engineering / OpenStack          | http://blog.oddbit.com/
>>