killercentury / docker-jenkins-dind

Generic Jenkins CI with Docker Engine and Docker Compose inside

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-jenkins-dind's Issues

Question about running docker inside docker and report result properly to jenkins dind instance

Im using docker-compose to setup my app containers and then run the tests but they do not properly report to jenkins when a tests fail do you know how to accomplish this??

im using python and unittest runner im running tests like this:

docker-compose up -d
docker exec -i workspace_wadev_1 python run_tests.py

Thanks in advance for your support

Port conflict?

When I try to access, I get a 503 error.
I've connected to the container. This is what I found:

root@jenkins:/# supervisord
/usr/lib/python2.7/dist-packages/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
  'Supervisord is running as root and it is searching '
2017-04-19 13:09:27,585 CRIT Supervisor running as root (no user in config file)
2017-04-19 13:09:27,585 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
Error: Another program is already listening on a port that one of our HTTP servers is configured to use.  Shut this program down first before starting supervisord.
For help, use /usr/bin/supervisord -h