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
On 6 April 2016 at 21:29, 'Torsten Kleiber' via Puppet Users
wrote:
> 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,
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
--
On 5 April 2016 at 14:47, 'Torsten Kleiber' via Puppet Users
wrote:
> 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
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 =>
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':
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',*