Re: [Puppet Users] When usion puppet docker_platform with vagrant virtualbox the docker container is not started and after restart the docker daemon is not started

2016-04-05 Thread Gareth Rushgrove
Hi Torsten The bold values represent the defaults, so you shouldn't need to specify them. You also have some other options set that I don't think are required. Could you try with the following: class { 'docker': } docker::image { 'jenkinsci/jenkins:2.0-beta-1': } docker::run { 'Jenkins2Beta1':

[Puppet Users] Unable to fetch my node definition, but the agent run will continue

2016-04-05 Thread Angel L. Mateo
Hello, I have a running puppetmaster with version 3.8.6. Now I'm trying to deploy a new puppetmaster 4 (using the puppetserver AIO package) that uses my current 3.8.6 puppetmaster as the CA. In this server's puppet.conf file I have: [main] ca_server = ... [master] autosign

Re: [Puppet Users] When usion puppet docker_platform with vagrant virtualbox the docker container is not started and after restart the docker daemon is not started

2016-04-05 Thread 'Torsten Kleiber' via Puppet Users
Hi Gareth! I had to add the bold line to start puppet successful: class { 'docker': } docker::image { 'jenkinsci/jenkins:2.0-beta-1': } docker::run { 'Jenkins2Beta1': * image=> 'jenkinsci/jenkins:2.0-beta-1',* ports=> '8080:8080', volumes => '/virtual_storage

Re: [Puppet Users] Announce: Puppet 3.8.5 available

2016-04-05 Thread Kylo Ginsberg
On Mon, Apr 4, 2016 at 10:42 AM, Christopher Wood < christopher_w...@pobox.com> wrote: > (Pardon the necro, I felt these interesting results should be filed with > the other ones.) > Thanks for the necro actually. It's much appreciated to see the real-world improvements. And ~20s to ~6s is a very