- From: Brian Akins <
>
- To: chef <
>
- Subject: [chef] Re: Re: Re: Chef with Docker and Chroot
- Date: Fri, 24 Jan 2014 08:05:53 -0500
In my "playing" with chef and docker, I've been just treating docker as a "package manager." I name/tag docker images like <product/deployment>-<version>. I also assume that the config variations are controlled via environment variables to docker (ala 12-factor).
So, in chef, I docker pull the image and setup a runit service that wraps docker run.
I don't have generic nginx/apache images, rather I create images that provide a "service" and name them as such. So, "thatsite-proxy" may be an image based on a generic nginx image, but has a config for "thatsite-proxy" and uses environment variables for variations. nginx is actually not a great example as it's mostly "code" I'm deploying - sinatra apps, go stuff, node, etc - that are created by a build system that spits out docker images.
This is all just me playing in my spare time and probably falls apart in the "real world."
Archive powered by MHonArc 2.6.16.