Prototype Docker usage for hosted-local runtime solution

[jmogarrio]

From Chat:

Benjamin Wulfe, 11:36 AM by the way, over the weekend I found out that colab has a docker image that may have all the packages in the hosted runtime (at least the docs claim it does!) https://research.google.com/colaboratory/local-runtimes.html

You can either run Jupyter directly or use Colab's Docker image. The Docker image includes packages found in our hosted runtime environments (https://colab.research.google.com/) and enables some UI features such as debugging and the resource utilization monitor. 

Benjamin Wulfe, 11:38 AM, Edited so we may be able to simply build for hosted and have it 'just work' for local by using the docker image. (including google drive support)

• [ ] Check if this gets rid of the issue in #39.

[jmogarrio]

Reviewing this more carefully I realized this is just a different solution for managing packages/environments for local runtimes. I'm discussing it in my update for go/ddf-runtimes.

What this could do is make it possible to use the google.colab module in local runtimes. Updating description.

[jmogarrio]

As far as I can tell, the Docker runtime in the documentation above is only usable via Colab. I ran the steps in the description, and was able to connect to it via Colab, but not via my localhost (I also can't connect via my IDE but that might be an issue with how local hosts are handled by my IDE). So it appears that the docker option might be feasible for providing access to local hardware, but not sure that it can close the gap between the convenience of Colab and the versatility of local runtimes (particularly beneficial for development).