Public | Automated Build

Last pushed: 2 days ago
Short Description
Generic Jenkins CI with Docker Engine and Docker Compose inside
Full Description

Jenkins DinD (Docker in Docker)

This Jenkins Docker image provides Docker inside itself, which allows you to run any Docker container in your Jenkins build script.

Because Docker container proivdes an isolated environment for running applications or tasks, which is perfect for any CI solution. This image is designed to run everything with Docker, so it doesn't pre-install any execution environment for any specific programming language. Instead, simply run the images you need from the public Docker Hub or your private Docker registry for your CI tasks.

This Docker image is based on jpetazzo/dind instead of the offical Jenkins. Supervisord is used to make sure everything has proper permission and lanuch in the right order. Morever, Docker Compose is available for launching multiple containers inside the CI.

Run it with mounted directory from host:

docker run --name jenkins-dind --privileged -d -p 8080:8080 -v /your/path:/var/lib/jenkins killercentury/jenkins-dind
Docker Pull Command

Comments (3)
2 years ago


  I've gotten a problem with mounting my directory to the container even I assigned "--privileged" directly when I run it. 
  Can u give me some help?

thanks a lot.
Kevin Yang

2 years ago

Instead of needing it to be interactive you could just manually add an entry for the git repository in ~/.ssh/known_hosts
If you try this on your local machine first you will easily be able to see what it should look like

2 years ago

thank you very much for this image!
I have one question...
Is it possible to get access to the jenkins command line client/log? (The thing that is open and accepts user input when you start jenkins via start script)
Because usually when I try to hook up a ssh git repository with jenkins it asks me whether to trust the key provided by the repository.
Now I have no option to say 'Yes I trust it'.