Teradata recommends 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, do not allow other users to access the same JupyterLab instance. Do not share your JupyterLab private token. Make sure, only a single user uses a single JupyterLab instance. 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 https://jupyterlab.readthedocs.io/en/stable/public_server.html before accessing JupyterLab Docker from a remote machine.
- Teradata recommends 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.
- Place the certificate files in a directory you bind to the /home/jovyan/certs directory (/path/to/my/certfile/directory in the following docker run command).
When the Docker image starts, the image detects the certificate files and starts up using HTTPS. You can also use Docker volume or different local directory to persist your notebooks as described before.
docker run -e "accept_license=Y" -p 8888:8888 -v /path/to/my/certfile/directory:/home/jovyan/certs -v teradata-vol:/home/jovyan/JupyterLabRoot teradatajupyterlabext
or
docker run -e "accept_license=Y" -p 8888:8888 -v /path/to/my/certfile/directory:/home/jovyan/certs -v /path/to/my/directory:/home/jovyan/JupyterLabRoot teradatajupyterlabext