Docker, does it make sense to use a provisioner?

Asked

Viewed 125 times

0

Next, I have done a more in-depth study on software provisioning with tools like Puppet, Chef and Ansible. I wonder if it makes sense to use them with Docker?

2 answers

4


Host side makes sense. It is possible to find Puppet modules to manage Docker containers.

On the client side, there is nothing yet very defined. There are basically two situations where configuration management can be used:

  • At the time of construction - creation of the container
  • At boot time - to finish setting, applying specific environment parameters, before initializing the process.

As an example, one can imagine a Dockerfile where Puppet is used, without the master, to perform some container configurations (construction time):

# Aqui é considerado que há uma imagem Centos com o Puppet disponível
FROM centos:puppet
ADD conf /etc/puppet/
RUN puppet apply -v -e 'include tomcat7_rhel'

Using such a tool at the time of initialization or even at the time of execution can be useful if it is necessary to perform some very complicated environment configuration.

There is still no consensus on the subject. Anyway, this implies dividing the classes / cookbooks to clearly separate into two executions, which is a great re-factoring.

  • Ok, very well explained, I see that for the host is valid the use. Thank you very much!

0

If you already have the recipes/ modules ready, maybe it makes sense yes, but if you are still building, I do not see so much need.

The idea of Ocker is to be as simple and declarative as possible, so making Dockerfile would be enough for their demands. Remember that Docker is not a lightweight virtual machine but a process running in a self-contained environment.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.