[chef] Re: Re: Re: Re: Re: chef-init (chef-container)

["Julian C. Dunn" < >]

On Sat, 27 Dec 2014, alambike wrote:

> I understand that to build docker images chef-init is a good start, but
> maybe to run the services inside the container (as PID 1) is a bit
> redundant, just because runit is enough to this task or because you dont
> want to run any proccess manager at all.
>
> Based on this I copy the patch to Chef service resource in my base cookbook
> and modify the runit provider to pull from system installation. Converging
> the image with this recipe in runlist works fine and if I want to rerun
> convergence inside a new or running container always can with 'docker exec'.
>
> Anyway, having a standard form to converge inside containers or just simply
> build docker images with chef I think would be useful. Chef provisioning
> looks good, but maybe its objetives are more general and more focused in
> cluster management, maybe chef-init could be a driver to docker/lxc
> platform in this context but I think that a form to converge chef recipes
> inside a container is still needeed.

Right, one of the things we were contemplating was to implement a way to 
have Chef Provisioning do the container convergence operations from 
outside the container, as you say, so the container itself is not 
burdened with the Chef client. We'll definitely be doing more research 
& development in this area in the new year.

- Julian

[ Julian C. Dunn 
<
 >
          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ;]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ;]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]