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 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':
ports=> '8080:8080',
volumes => '/virtual_storage/jenkins_home:/var/jenkins_home',
}
I think what is happening here is that by specifying detach you are
separating the docker container from the init script which is
generated by the module.
With regards to the docker daemon starting on boot, I think that's the
init scripts shipped with Docker. These vary depending on the OS
unfortunately. Puppet should be telling the service to be enabled:
https://github.com/garethr/garethr-docker/blob/master/manifests/service.pp#L198.
Let us know if that resolves your issue.
Gareth
On 4 April 2016 at 20:56, 'Torsten Kleiber' via Puppet Users
wrote:
> 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',
> }
> docker::image { 'jenkinsci/jenkins:2.0-beta-1':
> require => Class['docker'],
> }
>
> docker::run { 'Jenkins2Beta1':
> image=> 'jenkinsci/jenkins:2.0-beta-1',
> detach => true,
> ports=> '8080:8080',
> volumes => '/virtual_storage/jenkins_home:/var/jenkins_home',
> running => true,
> extra_parameters => ['--restart unless-stopped'],
> require => Docker::Image['jenkinsci/jenkins:2.0-beta-1'],
> }
>
> With the bold configuration I would expect the my container 'Jenkins2Beta1'
> should be started after provisioning, which is not the case.
> I have to determine the id of the container manual via "sudo docker ps -all"
> and start it then via "sudo docker start ".
>
> Furthermore after restarting the virtualbox machine via "vagrant halt" and
> "vagrant up" the docker daemon has to be started manually via "sudo docker
> daemon".
>
> What is wrong in my manifest?
>
> Kind regards
> Torsten
>
> --
> 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/389a99f5-793d-4448-8ffd-cd8adb7f6236%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_6yJxDbNUzDCnv9gjOBSxY3nyxu54s-mzeYST%2B1kvSBOD_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Unable to fetch my node definition, but the agent run will continue
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 = $confdir/autosign.conf { mode = 664 }
external_nodes = /etc/puppetlabs/puppet/node.rb
node_terminus = exec
ca = false
ssldir = /etc/puppetlabs/puppet/ssl
certname =
parser = current
strict_variables = false
The problem I have is that whenever I try to run puppet agent in this
same host I get:
# /opt/puppetlabs/bin/puppet agent -t --server puppetmaster> --environment feature_TLM_3240
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Find
/puppet/v3/node/mus30.um.es?environment=feature_TLM_3240&configured_environment=feature_TLM_3240&...
resulted in 404 with the message: Not Found: Could not find node of new puppetmaster>
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find node ''; cannot compile
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Any help? Is there any way I could debug this problem?
Thanks.
--
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información
y las Comunicaciones Aplicadas (ATICA)
http://www.um.es/atica
Tfo: 868887590
Fax: 86337
--
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/5703B454.40103%40um.es.
For more options, visit https://groups.google.com/d/optout.
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/jenkins_home:/var/jenkins_home',
}
But now I get following error:
==> default: Error: Could not start Service[docker]: Execution of
'/bin/systemctl start docker' returned 1: Job for docker.service failed
because the control process exited with error code. See "systemctl status
docker.service" and "journalctl -xe" for details.
==> default: Error: /Stage[main]/Docker::Service/Service[docker]/ensure:
change from stopped to running failed: Could not start Service[docker]:
Execution of '/bin/systemctl start docker' returned 1: Job for
docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
[vagrant@oraclelinux7 ~]$ systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor
preset: disabled)
Drop-In: /etc/systemd/system/docker.service.d
└─service-overrides.conf
Active: failed (Result: exit-code) since Tue 2016-04-05 23:23:37 AEST;
9min ago
Docs: https://docs.docker.com
Process: 10148 ExecStart=/usr/bin/docker -d -H fd:// $OPTIONS
$DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $BLOCK_REGISTRY
$INSECURE_REGISTRY (code=exited, status=125)
Main PID: 10148 (code=exited, status=125)
Apr 05 23:23:37 oraclelinux7.vagrant.vm systemd[1]: Starting Docker
Application Container Engine...
Apr 05 23:23:37 oraclelinux7.vagrant.vm docker[10148]: flag provided but
not defined: -d
Apr 05 23:23:37 oraclelinux7.vagrant.vm docker[10148]: See '/usr/bin/docker
--help'.
Apr 05 23:23:37 oraclelinux7.vagrant.vm systemd[1]: docker.service: main
process exited, code=exit...n/a
Apr 05 23:23:37 oraclelinux7.vagrant.vm systemd[1]: Failed to start Docker
Application Container Engine.
Apr 05 23:23:37 oraclelinux7.vagrant.vm systemd[1]: Unit docker.service
entered failed state.
Apr 05 23:23:37 oraclelinux7.vagrant.vm systemd[1]: docker.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
It seems, that -d is really not defined on Oracle Enterprise Linux, should
this be -D instead?
[vagrant@oraclelinux7 ~]$ /usr/bin/docker --help
Usage: docker [OPTIONS] COMMAND [arg...]
docker daemon [ --help | ... ]
docker [ --help | -v | --version ]
A self-sufficient runtime for containers.
Options:
--config=~/.docker Location of client config files
-D, --debug Enable debug mode
-H, --host=[] Daemon socket(s) to connect to
-h, --help Print usage
-l, --log-level=infoSet the logging level
--tls Use TLS; implied by --tlsverify
--tlscacert=~/.docker/ca.pemTrust certs signed only by this CA
--tlscert=~/.docker/cert.pemPath to TLS certificate file
--tlskey=~/.docker/key.pem Path to TLS key file
--tlsverify Use TLS and verify the remote
-v, --version Print version information and quit
Commands:
attachAttach to a running container
build Build an image from a Dockerfile
commitCreate a new image from a container's changes
cpCopy files/folders between a container and the local
filesystem
createCreate a new container
diff Inspect changes on a container's filesystem
eventsGet real time events from the server
exec Run a command in a running container
exportExport a container's filesystem as a tar archive
history Show the history of an image
imagesList images
importImport the contents from a tarball to create a filesystem
image
info Display system-wide information
inspect Return low-level information on a container or image
kill Kill a running container
load Load an image from a tar archive or STDIN
login Register or log in to a Docker registry
logoutLog out from a Docker registry
logs Fetch the logs of a container
network Manage Docker networks
pause Pause all processes within a container
port List port mappings or a specific mapping for the CONTAINER
psList containers
pull Pull an image or a repository from a registry
push Push an image or a repository to a registry
renameRename a container
restart Restart a container
rmRemove one or more containers
rmi Remove one or more images
run Run a command in a new container
save Save an image(s) to a tar archive
searchSearch the Docker Hub for images
start Start one or more stopped containers
stats
Re: [Puppet Users] Announce: Puppet 3.8.5 available
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 nice improvement! Kylo > > On Thu, Feb 11, 2016 at 08:50:32AM -0800, Kylo Ginsberg wrote: > >On Thu, Feb 11, 2016 at 8:02 AM, Christopher Wood > ><[1]christopher_w...@pobox.com> wrote: > > > > For idle interest's sake, I calculated the catalog compilation times > > across our puppetmasters on Thursday January 28th with (open source) > > 3.8.4 and did the same thing just now for Thursday February 4th with > > (open source) 3.8.5. > > > > Average catalog compilation times improved from 23.59 s to 20.44 s, > or > > approximately 13% improvement. > > > >\o/ > >We're giving more and more attention to performance improvements, so > glad > >to get data-driven feedback like this. Thanks! > >Kylo > > The above was all apache/passenger. > > After another upgrade the puppetmasters here have been running these since > Wednesday March 30th: > > [root@puppetmaster4 ~]# rpm -q puppetserver > puppetserver-2.2.1-1.el6.noarch > [root@puppetmaster4 ~]# rpm -q puppet-agent > puppet-agent-1.3.6-1.el6.x86_64 > > On Thursday March 31st catalog compilation times averaged 5.93 s across > all production puppetmasters. > > > > > On Wed, Jan 27, 2016 at 02:58:29PM -0800, Eric Sorenson wrote: > > >Puppet 3.8.5 is now available. This is a bugfix release that > > contains > > >performance improvements to catalog compilation and Mac OS X > > service > > >management, along with fixes for Windows agents and the Puppet > 4 > > language > > >parser. See the full release notes here: > > > > > [2] > http://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html > > >For installation and upgrade instructions, see this doc: > > >[3] > http://docs.puppetlabs.com/puppet/3.8/reference/pre_install.html > > >A special community shout-out for this release to Github user > > 'earsdown' > > >for the PR to fix PUP-5212, which added HTTP proxy support to > the > > PIP > > >package provider. > > >Eric Sorenson - [4]eric.soren...@puppetlabs.com - freenode > #puppet: > > eric0 > > >puppet platform // coffee // techno // bicycles > > > > > >-- > > >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 [1][5]puppet-users+unsubscr...@googlegroups.com. > > >To view this discussion on the web visit > > > > > [2][6] > https://groups.google.com/d/msgid/puppet-users/162976e8-f3a4-4af5-a211-a0900f3b4aa5%40googlegroups.com > . > > >For more options, visit [3][7] > https://groups.google.com/d/optout. > > > > > > References > > > > > >Visible links > > >1. mailto:[8]puppet-users+unsubscr...@googlegroups.com > > >2. > > [9] > https://groups.google.com/d/msgid/puppet-users/162976e8-f3a4-4af5-a211-a0900f3b4aa5%40googlegroups.com?utm_medium=email&utm_source=footer > > >3. [10]https://groups.google.com/d/optout > > -- > > 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 [11]puppet-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > [12] > https://groups.google.com/d/msgid/puppet-users/20160211160222.GA20645%40iniquitous.heresiarch.ca > . > > For more options, visit [13]https://groups.google.com/d/optout. > > > >-- > >Kylo Ginsberg | [14]k...@puppetlabs.com | irc: kylo | twitter: @kylog > > > >-- > >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 [15]puppet-users+unsubscr...@googlegroups.com. > >To view this discussion on the web visit > >[16] > https://groups.google.com/d/msgid/puppet-users/CALsUZFFewEebnPXbjezHhbwJpyxsSv7_HOba-W9XZ_MmMg6LpQ%40mail.gmail.com > . > >For more options, visit [17]https://groups.google.com/d/optout. > > > > References > > > >Visible links > >1. mailto:christopher_w...@pobox.com > >2. http://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html > >3. http://docs.puppetlabs.com/puppet/3.8/reference/pre_install.html > >4. mailto:eric.soren...@puppetlabs.com > >5. mailto:puppet-users%2bunsubscr...@googlegroups.com > >6. > https://groups.g
