On Sun, Jan 29, 2017 at 12:54:48PM -0500, Tom McKay wrote: > The foreman-docker container provisioning is not as richly featured as host > provisioning and it has me thinking what I would do differently. > > For my case I needed to "docker run" the container and then "docker exec" > several commands, and finally curl against it to configure. What I ended up > doing, which worked beautifully, was to make an ansible role that > accomplished all this plus additional steps of modifying the atomic host > the container was running on. Magic! > > I did run into some issues and limitations with foreman-ansible plugin (I > had to run ansible manually outside foreman) but overall ansible is the > tool for the job. > > Looking at the ansible modules around docker it's clear that even if I had > a nice wizard, if that wizard ended up generating me a playbook that I > could further modify it would be awesome. > > I have very little knowledge of puppet and provisioning but I feel that > wiring ansible into the container provisioning might be a very powerful > introduction to ansible for foreman users. > > Is this a realistic idea?
I'm wondering if it is a good idea. Containers should be stateless and I think what you're describing goes aginst that. For me the whole idea behind a docker container is that it's prebuilt. That's what Dockerfiles are for. In case you are describing building images, then I think Packer[1] does something similar to what you want. [1]: https://www.packer.io/docs/builders/docker.html -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
