Public | Automated Build

Last pushed: 5 months ago
Short Description
Short description is empty for this repo.
Full Description


A Docker image which allows for running Docker in Docker (DinD). This image is meant to be used with the Jenkins Docker plugin. It allows for Docker containers used as Jenkins build slaves to create and publish their own Docker images in-turn.

This is a mashup of "evarga/jenkins-slave" and "jpetazzo/dind".


  • The container must be run with --privileged in order for nested-Docker to work. There is a check box to enable this for the image within the Jenkins UI.


I have a write-up of how to use Docker containers as build slaves within Jenkins at:

Once your Jenkins slave is up and running, you can run docker commands like docker build, docker pull, and docker push from within the Docker build slave container.

Misc References

Docker Pull Command
Source Repository

Comments (6)
2 years ago

why your new version don't work?!!!!
root@c910c18b7427:/# ./

  • /usr/sbin/sshd -D
  • /usr/local/bin/wrapdocker
    mount: block device none is write-protected, mounting read-only
    mount: cannot mount block device none read-only
    Could not mount /sys/kernel/security.
    AppArmor detection and --privileged mode might break.
    mkdir: cannot create directory '/sys/fs/cgroup/name=systemd': Read-only file system
    mount: mount point /sys/fs/cgroup/name=systemd does not exist
    ln: failed to create symbolic link '/sys/fs/cgroup/systemd/name=systemd': Read-only file system
    INFO[0000] API listen on /var/run/docker.sock
    ERRO[0000] [graphdriver] prior storage driver "aufs" failed: permission denied
    FATA[0000] Error starting daemon: error initializing graphdriver: permission denied
2 years ago

Thanks :)

2 years ago

Another rebuild for docker 1.6 would be nice. Sorry to have to keep bugging you about it. :)

3 years ago

The Jenkins Docker plugin by default starts containers with the command /usr/sbin/sshd -D. In the "Docker Command" field you'll need to explicitly specify the command / for this container to work correctly.

I kept getting thrown off because I couldn't use the docker command in the container. Hopefully this helps anyone with similar issues.

3 years ago

@nubs - Started the build.

re: repo links - Wouldn't I want to link to "evarga/jenkins-slave" since that's what I'm inheriting from in my "FROM" statement?

3 years ago

Could you trigger a rebuild of this (maybe with a tag) so that Docker 1.5.0 gets used? It may make sense to add a repository link to jpetazzo/dind so this rebuilds whenever dind is rebuilt (kinda hacky, but makes some sense)