ENH: Add Dockerfile for development inside a container

[ColCarroll]

This is tweaking #1473 -- test suite works inside the container, and running . ./scripts/start_container.sh works on my machine.

It is ready to merge -- it does not change existing functionality (or add new features -- it is only for ease of development), but I can start a new 3.1 branch with this if we want to be strict about only bug fixes going into 3.0 @fonnesbeck.

[springcoil]

I think this is fine for 3.0

[AustinRochford]

Thanks for figuring this out @ColCarroll!

[twiecki]

typo then then

[twiecki]

Since this is just adding new code I think we should merge this into master after the typo is fixed.

[twiecki]

I added an auto-build to docker hub: https://hub.docker.com/r/pymc/pymc3/ (let me know if I should add you to the docker org).

So you don't have to build the image anymore, you can just do: docker pull pymc/pymc3

[twiecki]

docker run -d -p 8888:8888 pymc/pymc3

Brings up the jupyter notebook, but you can't import pymc3. I now realize that this docker image isn't meant to be used by a user, although we could easily extend/change it to do that.

[ColCarroll]

@twiecki interesting idea. what about building pymc in docker properly (i.e., pip installing it), and having a standalone pymc3-docker project? Then the start-container.sh file could still mount the local pymc and edit the $PYTHONPATH.

My worry is that since it is pretty easy to install, the docker image wouldn't be used, so there isn't much upside.

[twiecki]

Yeah, good point. Since we have it working on conda and linux is easy to begin with I agree with your assessment. In any case, we can use the dockerhub for easier debugging of travis problems now.