On 5 April 2016 at 14:47, 'Torsten Kleiber' via Puppet Users
<puppet-users@googlegroups.com> 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 => '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?
>
Ah. Docker 1.10 removed the -d flag in favour of the daemon subcommand.
This is fixed in the upstream module (garethr/docker). We should have
a release of docker_platform out soon with those fixes in. For the
moment I would suggest trying this out with the garethr/docker module
and see if that works. Alternatively you can pin to docker version 1.9
and that should work too.
Thanks
Gareth
> [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=info Set the logging level
> --tls Use TLS; implied by --tlsverify
> --tlscacert=~/.docker/ca.pem Trust certs signed only by this CA
> --tlscert=~/.docker/cert.pem Path 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:
> attach Attach to a running container
> build Build an image from a Dockerfile
> commit Create a new image from a container's changes
> cp Copy files/folders between a container and the local
> filesystem
> create Create a new container
> diff Inspect changes on a container's filesystem
> events Get real time events from the server
> exec Run a command in a running container
> export Export a container's filesystem as a tar archive
> history Show the history of an image
> images List images
> import Import 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
> logout Log 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
> ps List containers
> pull Pull an image or a repository from a registry
> push Push an image or a repository to a registry
> rename Rename a container
> restart Restart a container
> rm Remove 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
> search Search the Docker Hub for images
> start Start one or more stopped containers
> stats Display a live stream of container(s) resource usage
> statistics
> stop Stop a running container
> tag Tag an image into a repository
> top Display the running processes of a container
> unpause Unpause all processes within a container
> update Update resources of one or more containers
> version Show the Docker version information
> volume Manage Docker volumes
> wait Block until a container stops, then print its exit code
>
> Run 'docker COMMAND --help' for more information on a command.
>
> --
> 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/685674a9-e42a-4687-82ba-087eba6aed87%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_6yJApqtwbOgU3fJndB8Kj5u_RKSo5JPALKeabggbDxhZLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
