3 ms·

I follow that I'm not provisioning a full node, and parts of Chef installations are definitely unneeded, but where I'm stuck is I still have a config file that

by caw 12y ago

I follow that I'm not provisioning a full node, and parts of Chef installations are definitely unneeded, but where I'm stuck is I still have a config file that I need to control. In the case of Cassandra I'd have certain cassandra.yml tweaks I need to make, possibly different for beta/staging/prod, and docker-cassandra needs that config file. I also need to spawn the containers with the right setup, such that the right ports get exposed and shared volumes get mounted so the configs get read in. The spawning is a slightly different ops problem (do I want a homogenous cluster where I just spawn containers somewhere as needed, or do I want certain containers on certain machine types), but it seems like something that would fall in the domain of a provisioning tool. Should I just be building the configs into the container and rebuild the container if they need to change? The isolation of the process seems at odds with my desire to have a semi-dynamic, centrally managed configuration. I'm also considering that Chef itself is overkill to manage Docker containers and there are other tools more well suited to managing Docker-based infrastructure, but I'm not sure what they are.

hobofan 12y ago
I would go with building the config into the image and tagging the resulting image with the environment name, if that's possible. We've been using chef in the past to manage docker, which never felt very good because the main cookbook was somewhat buggy (but it has gotten better recently). We now use mesos+marathon(+chronos for deployment) for running our docker container, which sounds much more overkill than chef, but turned out to work much better and cleaner.
klochner 12y ago
Your best options are: a. environment varaibles (if that's an option) b. mount the file when you launch the container I'm using (b) for our nginx configs, you mount only the single config file as read-only, then let chef copy up the config before mounting/launching.
grosskur 12y ago
Take a look at confd, a single statically-linked executable that can expand config file templates using environment variables: https://github.com/kelseyhightower/confd https://github.com/kelseyhightower/confd Basically, you add confd into your Docker image and execute it at runtime to do just-in-time config file generation. Here's an example for nginx: https://github.com/grosskur/nginx-confd-dockerfile https://github.com/grosskur/nginx-confd-dockerfile You can create separate environment variable files for beta/staging/prod and pass --env-file to "docker run". This lets you use the same Docker image across all your environments and avoid the operational complexity of mounting config files in Docker volumes.
kraig 12y ago
You may want to look at how the docker-registry image is configured with environment variables. They have one image that can be used with files/S3/ceph/more configurations that are selected with variables. It's a pretty elegant way of having many configuration options in my opinion, except you still need to figure out how to 'docker run' the image. https://github.com/docker/docker-registry https://github.com/docker/docker-registry

by caw 12y ago

hobofan 12y ago

I would go with building the config into the image and tagging the resulting image with the environment name, if that's possible. We've been using chef in the past to manage docker, which never felt very good because the main cookbook was somewhat buggy (but it has gotten better recently). We now use mesos+marathon(+chronos for deployment) for running our docker container, which sounds much more overkill than chef, but turned out to work much better and cleaner.

klochner 12y ago

Your best options are: a. environment varaibles (if that's an option) b. mount the file when you launch the container I'm using (b) for our nginx configs, you mount only the single config file as read-only, then let chef copy up the config before mounting/launching.

grosskur 12y ago

Take a look at confd, a single statically-linked executable that can expand config file templates using environment variables: https://github.com/kelseyhightower/confd https://github.com/kelseyhightower/confd Basically, you add confd into your Docker image and execute it at runtime to do just-in-time config file generation. Here's an example for nginx: https://github.com/grosskur/nginx-confd-dockerfile https://github.com/grosskur/nginx-confd-dockerfile You can create separate environment variable files for beta/staging/prod and pass --env-file to "docker run". This lets you use the same Docker image across all your environments and avoid the operational complexity of mounting config files in Docker volumes.

kraig 12y ago

You may want to look at how the docker-registry image is configured with environment variables. They have one image that can be used with files/S3/ceph/more configurations that are selected with variables. It's a pretty elegant way of having many configuration options in my opinion, except you still need to figure out how to 'docker run' the image. https://github.com/docker/docker-registry https://github.com/docker/docker-registry