Add a Dockerfile for building Drone.io Docker containers.

[whitlockjc]

With the help/direction of @bradrydzewski and @crosbymichael, I have created the Dockerfile included in this commit. I've tested this locally and was able to successfully create a Docker container image for Drone and run it using Docker. This will be a huge help for people wanting to develop/run Drone without being on a Linux box.

I tested this on OS X 10.9.1 using boot2docker 0.5.4 and Docker 0.8.0.

[bradrydzewski]

great, merging now. did you try running a build? that might fail since it expects Docker to be running

[whitlockjc]

Here is what I've done to this point:

# Build the container
docker build -t whitlockjc/drone .

# Run the container
docker run -p 8080:80 whitlockjc/drone

Once the container is running, I could open http:https://localhost:8080/install on my host system and perform the Drone installation but I didn't actually perform a build. I'll do that and update accordingly.

[whitlockjc]

I guess I got a little too excited seeing Drone running. As I try to perform a build, I've hooked up to a GitHub repository but I don't see any way to configure a build or force it. With no documentation, this part will be hard to test. Got any tips?

[bradrydzewski]

add a .drone.yml file to your repository with your build configuration. There is some documentation in the README, however, I need to spend a lot more time improving the docs.

There is one issue. A build is triggered by a change to your repository, at which point GitHub sends a hook to Drone. Since you are running Drone locally (on localhost) GitHub will not be able to send the hook.

Since Drone is still very new, I really recommend testing Drone on Digital Ocean. You can get an Ubuntu server for $5 with Docker pre-installed with a static IP address. Check out this blog post someone put together:
http:https://jipiboily.com/2014/from-zero-to-fully-working-ci-server-in-less-than-10-minutes-with-drone-docker

I think having a Dockerfile is still really valuable

[whitlockjc]

Yup, that's the issue I was running into. The GitHub webhook is undeliverable. Makes sense. I'll work on getting a full roundtrip going but the usefulness of the Dockerfile is the same regardless. We might have to alter the Dockerfile a tad if something comes up but we won't know until we get there. I'll create a new PR if need be.

[afex]

you can use a service like https://ngrok.com/ to test github webhooks being sent to your locally running drone daemon

[whitlockjc]

Thanks @afex, that was just the tool I needed. Seems @bradrydzewski was right, the drone container cannot talk to docker: dial tcp 0.0.0.0:4243: connection refused. I'm sure you've ran into this before so if you have any tips, let me know.

[whitlockjc]

So, I was able to get build working. You need to use a Docker workaround for now (until introspection support is available). Here is the command to use: docker run -v /var/run/docker.sock:/var/run/docker.sock -p 8080:80 -d whitlockjc/drone