Access Docker Image for JupyterLab from a Remote Machine - 2.0 - About Accessing the Docker Image for JupyterLab from a Remote Machine - Teradata Vantage Modules for Jupyter

Teradata Vantageā„¢ Modules for Jupyter Installation Guide

Teradata Vantage Modules for Jupyter
March 2020

We recommend that you run the Docker image for JupyterLab and the browser on the same machine. You can access the Docker image from a browser running on a different machine.

Important: If you choose to deploy this configuration, it is important that you not allow other users to access the same JupyterLab instance. Do not share your JupyterLab private token. A single JupyterLab instance should only be used by a single user. Sharing the instance allows all resources to become available to other users, including result set data and connections.
If you choose to use a remote browser remember the following:
  • Consult the Jupyter documentation at before accessing JupyterLab Docker from a remote machine.
  • We recommend that you configure the Docker image to use HTTPS which requires a TLS certificate and key file. The certificate file must be named tlscert.pem, and the key file must be named tlskey.key.
  • The certificate files should be placed in a directory you bind to the /home/jovyan/certs directory ("/path/to/my/certfile/directory" in docker run command below). When the Docker image is started, it will detect the certificate files and will start up using HTTPS. You can also use Docker volume or different local directory to persist your notebooks as described above.

    docker run -p 8888:8888 -v /path/to/my/certfile/directory:/home/jovyan/certs -v teradata-vol:/home/jovyan/JupyterLabRoot teradatajupyterlabext


    docker run -p 8888:8888 -v /path/to/my/certfile/directory:/home/jovyan/certs -v /path/to/my/directory:/home/jovyan/JupyterLabRoot teradatajupyterlabext