On 4 June 2016 at 17:01, Thomas Müller <tho...@chaschperli.ch> wrote: > Hi Gareth >> >> >> >> * You want to run Puppet on something like CoreOS, PhotonOS or Atomic >> where containers are the defacto way of installing software >> * You want a full local development environment (including on WIndows >> or OSX) with minimal overhead >> >> The Dockerfiles and various build tools are available on GitHub: >> >> https://github.com/puppetlabs/puppet-in-docker >> > > Just at the right time. Wanted to start playing around with runnning a > master in a docker. >
Excellent, do let us know how you get on. > Browsing the Dockerfile on github I wondered why the config is not managed > by puppet (apply). I would have expected that after the agent is installed > that* everything else would be configured by Puppet manifests. > > Have not thought about it very long but it seems to me that managing the > config in puppet manifests would be cool. :-)I thinks of having a complete > control-repo style environment inside the Dockerfile directory to use with > puppet apply. > In the case of these initial images the amount of post package installation configuration is minimal, or in some cases even none [1]. So I stuck with a more Dockerfile native approach. I definitely think there are cases where Puppet makes a good tool for image configuration though. I was talking to a few folks about this example [2] using Rocker to avoid the resulting image size being too large just last week. I think one of the benefits (that might make this repository flip over to using Puppet later) would be the ability to create many images from a single Puppet codebase. This would avoid some of the repetition that often follows Dockerfiles around. I have some ideas for some quite nifty Puppet-native tooling here too. If anyone is going to be at DockerCon come and say Hi on the Puppet booth. I'm giving a talk about the pros and cons of Dockerfile, and on the need for higher level tools for image building that would probably be of interest. [1] https://github.com/puppetlabs/puppet-in-docker/blob/master/puppet-agent-ubuntu/Dockerfile [2] https://github.com/puppetlabs/puppet-rocker-demo [3] http://dockercon2016.sched.org/event/70Ng/the-dockerfile-explosion-and-the-need-for-higher-level-tools G > - Thomas > > * > https://github.com/puppetlabs/puppet-in-docker/blob/master/puppetserver-standalone/Dockerfile#L11 > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/ec6ddc1e-e66d-4151-b92f-0a8e05cc072b%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Gareth Rushgrove @garethr devopsweekly.com morethanseven.net garethrushgrove.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAFi_6yLyv3%2BrmPJea3_%2BByjhqVkhn81wC7fbRTxKQ-iZ1kTOXg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
