TL;DR
- I created docker image look-alike Google Colaboratory
- It is using the same OS version(Ubuntu17.10) as Google colaboratory.
- It is installed the same python library as Google colaboratory.
- You can use this docker image with “Local Runtime” feature of Google Colaboratory
Step to connect
- Setup nvidia-docker2
-
$ docker run --runtime=nvidia -it --rm -p 8081:8081 --cap-add SYS_ADMIN --device /dev/fuse --security-opt apparmor=unconfined ikeyasu/colab-local:latest-
--cap-add SYS_ADMIN,--device /dev/fuse,--security-optandapparmor=unconfinedare necessary for mounting Google drive. - You need to change port number, please change
-p 8081:8081. For example,-p 8082:8081if you want to use 8082.
-
- Click ▼ on top right of Colaboratory(next to "CONENCT" button), and click
- Input backend port to your docker instance like 8081. Then, click Connect button.
If a host running jupyter notebook is not localhost
Colaboratory requires localhost to connect local instance. If you would like to run jupyter notebook on another host, you need to use port-forwarding as follows.
$ ssh user@example.com -L 8081:localhost:8081
If you are using windows, you can use PuTTY.
What is benefit?
Google Colaboratory has many limitation, especially it could be ran by 12 hours only. In other hand, Google Colaboratory is good for first step of deep learning.
Thus, you can take a following step to move forward your project.
- Use Google Colaboratory for rough investigation and testing. It has limitation of 12 hours.
- If your model is looks good, launch Local Runtime. It does not have limitations. You can run a learning process for more 12 hours.
Docker image introduced this paper is looka-like Google Colaboratory. You don't need to concern a difference of environment between host runtime and local runtime.
Top comments (1)
Hi, great article :).
Do you know if the reverse would also be possible? I mean, connect a locally installed Jupyter Notebook to the runtime on Colab? (even if it has the same restrictions).