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-08 Thread 'Torsten Kleiber' via Puppet Users
Have changed now back to puppet-docker_platform a restrict to docker 1.9. Now all works fine. -- 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+unsub

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-06 Thread 'Torsten Kleiber' via Puppet Users
Hi Gareth! garethr/docker module does start the docker daemon after reboot via vagrant halt / up. But unfortunately the container does only exist and start after initial provisioning, but is not there anymore (via "sudo docker ps -all") after same vagrant restart. Kind regards Torsten -- You

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

[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-04 Thread 'Torsten Kleiber' via Puppet Users
Hi! I try to create a virtualbox machine with vagrant and puppet provider. According to the documentation https://forge.puppetlabs.com/puppetlabs/docker_platform/readme#class-docker I have create following manifest: class { 'docker': * service_enable => true,* * service_state => 'running',* }