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

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

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

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

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',* }

[Puppet Users] Re: "Connection timed out - connect(2)" when using puppet module

Am Dienstag, 17. Juni 2014 15:03:20 UTC+2 schrieb jcbollinger: > You mean you have set these in your puppet.conf or in your environment? > If the former then which one (file system path) and which section? Are you > running as root or as an unprivileged user? > I run at the moment with ro

[Puppet Users] Re: "Connection timed out - connect(2)" when using puppet module

Have nobody a hint? I have set http_proxy and https_proxy. curl -k *https://forgeapi.puppetlabs.com* is succesful. curl https://forgeapi.puppetlabs.com curl: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:S

[Puppet Users] "Connection timed out - connect(2)" when using puppet module

Hi! I try to install modules in puppet, but it gives an error message independent of the module I try to install: myserver:~ # puppet module install rtyler/jenkins Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Error: Coul

Re: [Puppet Users] SuSe SLES: error when refreshing puppet yum repository

The problem is rubygem itself, which was missing. This has to be installed from the SDK which was not available as repository on th system. Am Freitag, 13. Juni 2014 14:47:19 UTC+2 schrieb Darin Perusich: > rubygem-ruby-shadow is available in the repo so I don't know what > could be causing tha

Re: [Puppet Users] SuSe SLES: error when refreshing puppet yum repository

BTW: I try to install via following command, because of the double puppet in another repository: zypper --non-interactive install --repo puppet puppet -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop recei

Re: [Puppet Users] SuSe SLES: error when refreshing puppet yum repository

Could it be related to the fact, that I'm on patchset 1 or that old puppet 2.6 seems to exist in one of the other repositories? Here is the outpput: myserver:~ # zypper info rubygem-ruby-shadow Loading repository data... Reading installed packages... Information for package rubygem-ruby-shadow:

Re: [Puppet Users] SuSe SLES: error when refreshing puppet yum repository

Thanks for this! zypper refresh with this repo is now successful. But now I get another error: myserver:~ # zypper --non-interactive install --repo puppet puppet Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides rubygems needed by

Re: [Puppet Users] SuSe SLES: error when refreshing puppet yum repository

Thank you! But now I get another error: vdu10272:~ # zypper --non-interactive refresh Retrieving repository 'puppet' metadata [/] Download (curl) error for 'https://build.opensuse.org/project/show/systemsmanagement:puppet/repodata/repomd.xml': Error code: Unrecognized error Error message: SSL

[Puppet Users] SuSe SLES: error when refreshing puppet yum repository

Hi! I try to activate the yum repository for SUSE Linux Enterprise Server 11: myserver:~ # zypper --non-interactive addrepo -t YUM http://yum.puppetlabs.com puppet Adding repository 'puppet' [done] Repository 'puppet' successfully added Enabled: Yes Autorefresh: No URI: http://yum.puppetlabs.c