mirror of
https://github.com/jupyter/docker-stacks.git
synced 2025-10-08 10:34:06 +00:00
More docs cleanup
This commit is contained in:
Ayaz Salikhov
2
.github/ISSUE_TEMPLATE/bug_report.md
vendored
2
.github/ISSUE_TEMPLATE/bug_report.md
vendored
@@ -16,7 +16,7 @@ Example: `jupyter/scipy-notebook`
|
||||
|
||||
**What complete docker command do you run to launch the container (omitting sensitive values)?**
|
||||
|
||||
Example: `docker run -it --rm -p 8888:8888 jupyter/all-spark-notebook:latest`
|
||||
Example: `docker run -it --rm -p 8888:8888 jupyter/all-spark-notebook`
|
||||
|
||||
**What steps do you take once the container is running to reproduce the issue?**
|
||||
|
||||
|
||||
6
Makefile
6
Makefile
@@ -191,11 +191,11 @@ push-all-multi: $(foreach I, $(MULTI_IMAGES), push-multi/$(I)) $(foreach I, $(AM
|
||||
|
||||
|
||||
|
||||
run/%: ## run a bash in interactive mode in a stack
|
||||
run-shell/%: ## run a bash in interactive mode in a stack
|
||||
docker run -it --rm $(OWNER)/$(notdir $@) $(SHELL)
|
||||
|
||||
run-sudo/%: ## run a bash in interactive mode as root in a stack
|
||||
docker run -it --rm -u root $(OWNER)/$(notdir $@) $(SHELL)
|
||||
run-sudo-shell/%: ## run a bash in interactive mode as root in a stack
|
||||
docker run -it --rm --user root $(OWNER)/$(notdir $@) $(SHELL)
|
||||
|
||||
|
||||
|
||||
|
||||
10
README.md
10
README.md
@@ -9,8 +9,9 @@
|
||||
Jupyter Docker Stacks are a set of ready-to-run [Docker images](https://hub.docker.com/u/jupyter) containing Jupyter applications and interactive computing tools.
|
||||
You can use a stack image to do any of the following (and more):
|
||||
|
||||
- Start a personal Jupyter Server with JupyterLab frontend (default)
|
||||
- Run JupyterLab for a team using JupyterHub
|
||||
- Start a personal Jupyter Notebook server in a local Docker container
|
||||
- Run JupyterLab servers for a team using JupyterHub
|
||||
- Write your own project Dockerfile
|
||||
|
||||
## Quick Start
|
||||
@@ -48,7 +49,7 @@ This command pulls the `jupyter/datascience-notebook` image tagged `b418b67c225b
|
||||
It then starts an _ephemeral_ container running a Jupyter Server and exposes the server on host port 10000.
|
||||
|
||||
```bash
|
||||
docker run --rm -p 10000:8888 -v "${PWD}":/home/jovyan/work jupyter/datascience-notebook:b418b67c225b
|
||||
docker run -it --rm -p 10000:8888 -v "${PWD}":/home/jovyan/work jupyter/datascience-notebook:b418b67c225b
|
||||
```
|
||||
|
||||
The use of the `-v` flag in the command mounts the current working directory on the host (`{PWD}` in the example command) as `/home/jovyan/work` in the container.
|
||||
@@ -58,6 +59,7 @@ Visiting `http://<hostname>:10000/?token=<token>` in a browser loads JupyterLab.
|
||||
|
||||
Due to the usage of [the flag `--rm`](https://docs.docker.com/engine/reference/run/#clean-up---rm) Docker automatically cleans up the container and removes the file
|
||||
system when the container exits, but any changes made to the `~/work` directory and its files in the container will remain intact on the host.
|
||||
[The `-it` flag](https://docs.docker.com/engine/reference/commandline/run/#assign-name-and-allocate-pseudo-tty---name--it) allocates pseudo-TTY.
|
||||
|
||||
## Contributing
|
||||
|
||||
@@ -86,8 +88,8 @@ We will happily grant additional permissions (e.g., ability to merge PRs) to any
|
||||
|
||||
Following [Jupyter Notebook notice](https://github.com/jupyter/notebook#notice), JupyterLab is now the default for all of the Jupyter Docker stack images.
|
||||
It is still possible to switch back to Jupyter Notebook (or to launch a different startup command).
|
||||
You can achieve this by passing the environment variable `DOCKER_STACKS_JUPYTER_CMD=notebook` (or any other valid `jupyter` command) at container startup,
|
||||
more information is available in the [documentation](https://jupyter-docker-stacks.readthedocs.io/en/latest/using/common.html#docker-options).
|
||||
You can achieve this by passing the environment variable `DOCKER_STACKS_JUPYTER_CMD=notebook` (or any other valid `jupyter` subcommand) at container startup,
|
||||
more information is available in the [documentation](https://jupyter-docker-stacks.readthedocs.io/en/latest/using/common.html#alternative-commands).
|
||||
|
||||
According to the Jupyter Notebook project status and its compatibility with JupyterLab,
|
||||
these Docker images may remove the classic Jupyter Notebook interface altogether in favor of another _classic-like_ UI built atop JupyterLab.
|
||||
|
||||
@@ -1,29 +1,29 @@
|
||||
# Common Features
|
||||
|
||||
By default, a container launched from any Jupyter Docker Stacks image runs a Jupyter Notebook server.
|
||||
By default, a container launched from any Jupyter Docker Stacks image runs a Jupyter Server with JupyterLab frontend.
|
||||
The container does so by executing a `start-notebook.sh` script.
|
||||
This script configures the internal container environment and then runs `jupyter notebook`, passing any command line arguments received.
|
||||
This script configures the internal container environment and then runs `jupyter lab`, passing any command line arguments received.
|
||||
|
||||
This page describes the options supported by the startup script and how to bypass it to run alternative commands.
|
||||
|
||||
## Notebook Options
|
||||
## Jupyter Server Options
|
||||
|
||||
You can pass [Jupyter command line options](https://jupyter-notebook.readthedocs.io/en/stable/config.html#options) to the `start-notebook.sh` script when launching the container.
|
||||
For example, to secure the Notebook server with a custom password hashed using `IPython.lib.passwd()` instead of the default token, you can run the following:
|
||||
You can pass [Jupyter server options](https://jupyter-notebook.readthedocs.io/en/stable/public_server.html) to the `start-notebook.sh` script when launching the container.
|
||||
|
||||
```bash
|
||||
docker run -d -p 8888:8888 \
|
||||
jupyter/base-notebook start-notebook.sh \
|
||||
--NotebookApp.password='sha1:74ba40f8a388:c913541b7ee99d15d5ed31d4226bf7838f83a50e'
|
||||
```
|
||||
1. For example, to secure the Notebook server with a custom password hashed using `IPython.lib.passwd()` instead of the default token,
|
||||
you can run the following (this hash was generated for `my-password` password):
|
||||
|
||||
For example, to set the base URL of the notebook server, you can run the following:
|
||||
```bash
|
||||
docker run -it --rm -p 8888:8888 jupyter/base-notebook \
|
||||
start-notebook.sh --NotebookApp.password='sha1:7cca89c48283:e3c1f9fbc06d1d2aa59555dfd5beed925e30dd2c'
|
||||
```
|
||||
|
||||
```bash
|
||||
docker run -d -p 8888:8888 \
|
||||
jupyter/base-notebook start-notebook.sh \
|
||||
--NotebookApp.base_url=/some/path
|
||||
```
|
||||
2. To set the [base URL](https://jupyter-notebook.readthedocs.io/en/stable/public_server.html#running-the-notebook-with-a-customized-url-prefix) of the notebook server, you can run the following:
|
||||
|
||||
```bash
|
||||
docker run -it --rm -p 8888:8888 jupyter/base-notebook \
|
||||
start-notebook.sh --NotebookApp.base_url=/customized/url/prefix/
|
||||
```
|
||||
|
||||
## Docker Options
|
||||
|
||||
@@ -42,9 +42,13 @@ You do so by passing arguments to the `docker run` command.
|
||||
Example usage:
|
||||
|
||||
```bash
|
||||
docker run --rm -it -p 8888:8888 \
|
||||
-e NB_USER="my-username" -e CHOWN_HOME=yes \
|
||||
-w "/home/${NB_USER}" --user root jupyter/base-notebook:latest
|
||||
docker run -it --rm \
|
||||
-p 8888:8888 \
|
||||
--user root \
|
||||
-e NB_USER="my-username" \
|
||||
-e CHOWN_HOME=yes \
|
||||
-w "/home/${NB_USER}" \
|
||||
jupyter/base-notebook
|
||||
```
|
||||
|
||||
- `-e NB_UID=<numeric uid>` - Instructs the startup script to switch the numeric user ID of `${NB_USER}` to the given value.
|
||||
@@ -104,7 +108,8 @@ You do so by passing arguments to the `docker run` command.
|
||||
|
||||
### Additional runtime configurations
|
||||
|
||||
- `-e GEN_CERT=yes` - Instructs the startup script to generate a self-signed SSL certificate and configure Jupyter Notebook to use it to accept encrypted HTTPS connections.
|
||||
- `-e GEN_CERT=yes` - Instructs the startup script to generate a self-signed SSL certificate.
|
||||
Configures Jupyter Server to use it to accept encrypted HTTPS connections.
|
||||
- `-e DOCKER_STACKS_JUPYTER_CMD=<jupyter command>` - Instructs the startup script to run `jupyter ${DOCKER_STACKS_JUPYTER_CMD}` instead of the default `jupyter lab` command.
|
||||
See [Switching back to the classic notebook or using a different startup command][switch_back] for available options.
|
||||
This setting is helpful in container orchestration environments where setting environment variables is more straightforward than changing command line parameters.
|
||||
@@ -115,29 +120,31 @@ You do so by passing arguments to the `docker run` command.
|
||||
**You must grant the within-container notebook user or group (`NB_UID` or `NB_GID`) write access to the host directory (e.g., `sudo chown 1000 /some/host/folder/for/work`).**
|
||||
- `-e JUPYTER_ENV_VARS_TO_UNSET=ADMIN_SECRET_1,ADMIN_SECRET_2` - Unsets specified environment variables in the default startup script.
|
||||
The variables are unset after the hooks have been executed but before the command provided to the startup script runs.
|
||||
- `-e NOTEBOOK_ARGS="--log-level='DEBUG' --dev-mode"` - Adds custom options to launch `jupyter lab` or `jupyter notebook`. This way, the user could use any option supported by `jupyter`.
|
||||
- `-e NOTEBOOK_ARGS="--log-level='DEBUG' --dev-mode"` - Adds custom options to add to `jupyter` commands.
|
||||
This way, the user could use any option supported by `jupyter` subcommand.
|
||||
|
||||
## Startup Hooks
|
||||
|
||||
You can further customize the container environment by adding shell scripts (`*.sh`) to be sourced
|
||||
or executables (`chmod +x`) to be run to the paths below:
|
||||
|
||||
- `/usr/local/bin/start-notebook.d/` - handled before any of the standard options noted above
|
||||
are applied
|
||||
- `/usr/local/bin/before-notebook.d/` - handled after all of the standard options noted above are applied and ran right before the notebook server launches
|
||||
- `/usr/local/bin/start-notebook.d/` - handled **before** any of the standard options noted above are applied
|
||||
- `/usr/local/bin/before-notebook.d/` - handled **after** all of the standard options noted above are applied
|
||||
and ran right before the notebook server launches
|
||||
|
||||
See the `run-hooks` function in the [`jupyter/base-notebook start.sh`](https://github.com/jupyter/docker-stacks/blob/master/base-notebook/start.sh)
|
||||
script for execution details.
|
||||
|
||||
## SSL Certificates
|
||||
|
||||
You may mount an SSL key and certificate file into a container and configure the Jupyter Notebook to use them to accept HTTPS connections.
|
||||
You may mount an SSL key and certificate file into a container and configure the Jupyter Server to use them to accept HTTPS connections.
|
||||
For example, to mount a host folder containing a `notebook.key` and `notebook.crt` and use them, you might run the following:
|
||||
|
||||
```bash
|
||||
docker run -d -p 8888:8888 \
|
||||
docker run -it --rm -p 8888:8888 \
|
||||
-v /some/host/folder:/etc/ssl/notebook \
|
||||
jupyter/base-notebook start-notebook.sh \
|
||||
jupyter/base-notebook \
|
||||
start-notebook.sh \
|
||||
--NotebookApp.keyfile=/etc/ssl/notebook/notebook.key \
|
||||
--NotebookApp.certfile=/etc/ssl/notebook/notebook.crt
|
||||
```
|
||||
@@ -146,9 +153,10 @@ Alternatively, you may mount a single PEM file containing both the key and certi
|
||||
For example:
|
||||
|
||||
```bash
|
||||
docker run -d -p 8888:8888 \
|
||||
docker run -it --rm -p 8888:8888 \
|
||||
-v /some/host/folder/notebook.pem:/etc/ssl/notebook.pem \
|
||||
jupyter/base-notebook start-notebook.sh \
|
||||
jupyter/base-notebook \
|
||||
start-notebook.sh \
|
||||
--NotebookApp.certfile=/etc/ssl/notebook.pem
|
||||
```
|
||||
|
||||
@@ -188,13 +196,15 @@ Example:
|
||||
|
||||
```bash
|
||||
# Run Jupyter Notebook on Jupyter Server
|
||||
docker run -it --rm -p 8888:8888 \
|
||||
docker run -it --rm \
|
||||
-p 8888:8888 \
|
||||
-e DOCKER_STACKS_JUPYTER_CMD=notebook \
|
||||
jupyter/base-notebook
|
||||
# Executing the command: jupyter notebook ...
|
||||
|
||||
# Run Jupyter Notebook classic
|
||||
docker run -it --rm -p 8888:8888 \
|
||||
docker run -it --rm \
|
||||
-p 8888:8888 \
|
||||
-e DOCKER_STACKS_JUPYTER_CMD=nbclassic \
|
||||
jupyter/base-notebook
|
||||
# Executing the command: jupyter nbclassic ...
|
||||
@@ -210,12 +220,6 @@ For example, to run the text-based `ipython` console in a container, do the foll
|
||||
docker run -it --rm jupyter/base-notebook start.sh ipython
|
||||
```
|
||||
|
||||
Or, to run Jupyter Notebook classic instead of JupyterLab, run the following:
|
||||
|
||||
```bash
|
||||
docker run -it --rm -p 8888:8888 jupyter/base-notebook start.sh jupyter notebook
|
||||
```
|
||||
|
||||
This script is handy when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
|
||||
|
||||
### Others
|
||||
@@ -230,7 +234,7 @@ The `/opt/conda/bin` directory is part of the default `jovyan` user's `${PATH}`.
|
||||
That directory is also searched for binaries when run using `sudo` (`sudo my_binary` will search for `my_binary` in `/opt/conda/bin/`
|
||||
|
||||
The `jovyan` user has full read/write access to the `/opt/conda` directory.
|
||||
You can use either `pip`, `conda` or `mamba` to install new packages without any additional permissions.
|
||||
You can use either `mamba`, `pip` or `conda` (`mamba` is recommended) to install new packages without any additional permissions.
|
||||
|
||||
```bash
|
||||
# install a package into the default (python 3.x) environment and cleanup after
|
||||
|
||||
@@ -9,13 +9,15 @@ The sections below capture this knowledge.
|
||||
Password authentication is disabled for the `NB_USER` (e.g., `jovyan`).
|
||||
We made this choice to avoid distributing images with a weak default password that users ~might~ will forget to change before running a container on a publicly accessible host.
|
||||
|
||||
You can grant the within-container `NB_USER` passwordless `sudo` access by adding `-e GRANT_SUDO=yes` and `--user root` to your Docker command line or appropriate container orchestrator config.
|
||||
You can grant the within-container `NB_USER` passwordless `sudo` access by adding `--user root` and `-e GRANT_SUDO=yes` to your Docker command line or appropriate container orchestrator config.
|
||||
|
||||
For example:
|
||||
|
||||
```bash
|
||||
docker run -it -e GRANT_SUDO=yes \
|
||||
--user root jupyter/minimal-notebook
|
||||
docker run -it --rm \
|
||||
--user root \
|
||||
-e GRANT_SUDO=yes \
|
||||
jupyter/minimal-notebook
|
||||
```
|
||||
|
||||
**You should only enable `sudo` if you trust the user and/or if the container is running on an isolated host.**
|
||||
@@ -167,7 +169,8 @@ docker build -t jupyter/scipy-dasklabextension:latest .
|
||||
Once built, run using the command:
|
||||
|
||||
```bash
|
||||
docker run -it --rm -p 8888:8888 \
|
||||
docker run -it --rm \
|
||||
-p 8888:8888 \
|
||||
-p 8787:8787 jupyter/scipy-dasklabextension:latest
|
||||
```
|
||||
|
||||
@@ -484,14 +487,16 @@ In this case, you should use the `start.sh` script to launch the server with no
|
||||
For JupyterLab:
|
||||
|
||||
```bash
|
||||
docker run jupyter/base-notebook:b418b67c225b \
|
||||
docker run -it --rm \
|
||||
jupyter/base-notebook:b418b67c225b \
|
||||
start.sh jupyter lab --LabApp.token=''
|
||||
```
|
||||
|
||||
For jupyter classic:
|
||||
|
||||
```bash
|
||||
docker run jupyter/base-notebook:b418b67c225b \
|
||||
docker run -it --rm \
|
||||
jupyter/base-notebook:b418b67c225b \
|
||||
start.sh jupyter notebook --NotebookApp.token=''
|
||||
```
|
||||
|
||||
|
||||
@@ -18,42 +18,35 @@ It then starts a container running a Jupyter Notebook server and exposes the ser
|
||||
The server logs appear in the terminal and include a URL to the notebook server.
|
||||
|
||||
```bash
|
||||
docker run -p 8888:8888 jupyter/scipy-notebook:b418b67c225b
|
||||
docker run -it -p 8888:8888 jupyter/scipy-notebook:b418b67c225b
|
||||
|
||||
# Executing the command: jupyter notebook
|
||||
# [I 15:33:00.567 NotebookApp] Writing notebook server cookie secret to /home/jovyan/.local/share/jupyter/runtime/notebook_cookie_secret
|
||||
# [W 15:33:01.084 NotebookApp] WARNING: The notebook server is listening on all IP addresses and not using encryption. This is not recommended.
|
||||
# [I 15:33:01.150 NotebookApp] JupyterLab alpha preview extension loaded from /opt/conda/lib/python3.6/site-packages/jupyterlab
|
||||
# [I 15:33:01.150 NotebookApp] JupyterLab application directory is /opt/conda/share/jupyter/lab
|
||||
# [I 15:33:01.155 NotebookApp] Serving notebooks from local directory: /home/jovyan
|
||||
# [I 15:33:01.156 NotebookApp] 0 active kernels
|
||||
# [I 15:33:01.156 NotebookApp] The Jupyter Notebook is running at:
|
||||
# [I 15:33:01.157 NotebookApp] http://[all ip addresses on your system]:8888/?token=112bb073331f1460b73768c76dffb2f87ac1d4ca7870d46a
|
||||
# [I 15:33:01.157 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
|
||||
# [C 15:33:01.160 NotebookApp]
|
||||
# Entered start.sh with args: jupyter lab
|
||||
|
||||
# Copy/paste this URL into your browser when you connect for the first time,
|
||||
# to login with a token:
|
||||
# http://localhost:8888/?token=112bb073331f1460b73768c76dffb2f87ac1d4ca7870d46a
|
||||
# ...
|
||||
|
||||
# To access the server, open this file in a browser:
|
||||
# file:///home/jovyan/.local/share/jupyter/runtime/jpserver-7-open.html
|
||||
# Or copy and paste one of these URLs:
|
||||
# http://042fc8ac2b0c:8888/lab?token=f31f2625f13d131f578fced0fc76b81d10f6c629e92c7099
|
||||
# or http://127.0.0.1:8888/lab?token=f31f2625f13d131f578fced0fc76b81d10f6c629e92c7099
|
||||
```
|
||||
|
||||
Pressing `Ctrl-C` shuts down the notebook server but leaves the container intact on disk for later restart or permanent deletion using commands like the following:
|
||||
Pressing `Ctrl-C` twice shuts down the notebook server but leaves the container intact on disk for later restart or permanent deletion using commands like the following:
|
||||
|
||||
```bash
|
||||
# list containers
|
||||
docker ps -a
|
||||
# CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||||
# d67fe77f1a84 jupyter/base-notebook "tini -- start-noteb…" 44 seconds ago Exited (0) 39 seconds ago cocky_mirzakhani
|
||||
# 221331c047c4 jupyter/scipy-notebook:b418b67c225b "tini -g -- start-no…" 11 seconds ago Exited (0) 8 seconds ago cranky_benz
|
||||
|
||||
# start the stopped container
|
||||
docker start -a d67fe77f1a84
|
||||
# Executing the command: jupyter notebook
|
||||
# [W 16:45:02.020 NotebookApp] WARNING: The notebook server is listening on all IP addresses and not using encryption. This is not recommended.
|
||||
docker start -a 221331c047c4
|
||||
# Entered start.sh with args: jupyter lab
|
||||
# ...
|
||||
|
||||
# remove the stopped container
|
||||
docker rm d67fe77f1a84
|
||||
# d67fe77f1a84
|
||||
docker rm 221331c047c4
|
||||
# 221331c047c4
|
||||
```
|
||||
|
||||
**Example 2** This command pulls the `jupyter/r-notebook` image tagged `b418b67c225b` from Docker Hub if it is not already present on the local host.
|
||||
@@ -61,31 +54,16 @@ It then starts a container running a Jupyter Notebook server and exposes the ser
|
||||
The server logs appear in the terminal and include a URL to the notebook server, but with the internal container port (8888) instead of the the correct host port (10000).
|
||||
|
||||
```bash
|
||||
docker run --rm -p 10000:8888 -v "${PWD}":/home/jovyan/work jupyter/r-notebook:b418b67c225b
|
||||
|
||||
# Executing the command: jupyter notebook
|
||||
# [I 19:31:09.573 NotebookApp] Writing notebook server cookie secret to /home/jovyan/.local/share/jupyter/runtime/notebook_cookie_secret
|
||||
# [W 19:31:11.930 NotebookApp] WARNING: The notebook server is listening on all IP addresses and not using encryption. This is not recommended.
|
||||
# [I 19:31:12.085 NotebookApp] JupyterLab alpha preview extension loaded from /opt/conda/lib/python3.6/site-packages/jupyterlab
|
||||
# [I 19:31:12.086 NotebookApp] JupyterLab application directory is /opt/conda/share/jupyter/lab
|
||||
# [I 19:31:12.117 NotebookApp] Serving notebooks from local directory: /home/jovyan
|
||||
# [I 19:31:12.117 NotebookApp] 0 active kernels
|
||||
# [I 19:31:12.118 NotebookApp] The Jupyter Notebook is running at:
|
||||
# [I 19:31:12.119 NotebookApp] http://[all ip addresses on your system]:8888/?token=3b8dce890cb65570fb0d9c4a41ae067f7604873bd604f5ac
|
||||
# [I 19:31:12.120 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
|
||||
# [C 19:31:12.122 NotebookApp]
|
||||
|
||||
# Copy/paste this URL into your browser when you connect for the first time,
|
||||
# to login with a token:
|
||||
# http://localhost:8888/?token=3b8dce890cb65570fb0d9c4a41ae067f7604873bd604f5ac
|
||||
docker run -it --rm -p 10000:8888 -v "${PWD}":/home/jovyan/work jupyter/r-notebook:b418b67c225b
|
||||
```
|
||||
|
||||
Pressing `Ctrl-C` shuts down the notebook server and immediately destroys the Docker container.
|
||||
Pressing `Ctrl-C` twice shuts down the notebook server and immediately destroys the Docker container.
|
||||
Files written to `~/work` in the container remain touched.
|
||||
Any other changes made in the container are lost.
|
||||
|
||||
**Example 3** This command pulls the `jupyter/all-spark-notebook` image currently tagged `latest` from Docker Hub if an image tagged `latest` is not already present on the local host.
|
||||
It then starts a container named `notebook` running a JupyterLab server and exposes the server on a randomly selected port.
|
||||
The `-d` flag mean to run the container in detached mode.
|
||||
|
||||
```bash
|
||||
docker run -d -P --name notebook jupyter/all-spark-notebook
|
||||
@@ -96,16 +74,17 @@ The assigned port and notebook server token are visible using other Docker comma
|
||||
```bash
|
||||
# get the random host port assigned to the container port 8888
|
||||
docker port notebook 8888
|
||||
# 0.0.0.0:32769
|
||||
# 0.0.0.0:49153
|
||||
# :::49153
|
||||
|
||||
# get the notebook token from the logs
|
||||
docker logs --tail 3 notebook
|
||||
# Copy/paste this URL into your browser when you connect for the first time,
|
||||
# to login with a token:
|
||||
# http://localhost:8888/?token=15914ca95f495075c0aa7d0e060f1a78b6d94f70ea373b00
|
||||
# Or copy and paste one of these URLs:
|
||||
# http://878f1a9b4dfa:8888/lab?token=d336fa63c03f064ff15ce7b269cab95b2095786cf9ab2ba3
|
||||
# or http://127.0.0.1:8888/lab?token=d336fa63c03f064ff15ce7b269cab95b2095786cf9ab2ba3
|
||||
```
|
||||
|
||||
Together, the URL to visit on the host machine to access the server in this case is <http://localhost:32769?token=15914ca95f495075c0aa7d0e060f1a78b6d94f70ea373b00>.
|
||||
Together, the URL to visit on the host machine to access the server in this case is <http://127.0.0.1:49153/lab?token=d336fa63c03f064ff15ce7b269cab95b2095786cf9ab2ba3>.
|
||||
|
||||
The container runs in the background until stopped and/or removed by additional Docker commands.
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ set -e
|
||||
: "${SECRETS_VOLUME:=my-notebook-secrets}"
|
||||
docker volume create --name "${SECRETS_VOLUME}" 1>/dev/null
|
||||
# Generate the cert and save it to the Docker volume
|
||||
docker run --rm -it \
|
||||
docker run -it --rm \
|
||||
-p 80:80 \
|
||||
-v "${SECRETS_VOLUME}":/etc/letsencrypt \
|
||||
quay.io/letsencrypt/letsencrypt:latest \
|
||||
@@ -41,7 +41,7 @@ docker run --rm -it \
|
||||
# Set permissions so nobody can read the cert and key.
|
||||
# Also symlink the certs into the root of the /etc/letsencrypt
|
||||
# directory so that the FQDN doesn't have to be known later.
|
||||
docker run --rm -it \
|
||||
docker run -it --rm \
|
||||
-v "${SECRETS_VOLUME}":/etc/letsencrypt \
|
||||
ubuntu:20.04 \
|
||||
bash -c "ln -s /etc/letsencrypt/live/${FQDN}/* /etc/letsencrypt/ && \
|
||||
|
||||
@@ -54,21 +54,6 @@ You can now run the image.
|
||||
|
||||
```bash
|
||||
docker run --rm -p 8888:8888 notebook-examples
|
||||
# Executing the command: jupyter notebook
|
||||
# [I 01:14:50.532 NotebookApp] Writing notebook server cookie secret to /home/jovyan/.local/share/jupyter/runtime/notebook_cookie_secret
|
||||
# [W 01:14:50.724 NotebookApp] WARNING: The notebook server is listening on all IP addresses and not using encryption. This is not recommended.
|
||||
# [I 01:14:50.747 NotebookApp] JupyterLab beta preview extension loaded from /opt/conda/lib/python3.6/site-packages/jupyterlab
|
||||
# [I 01:14:50.747 NotebookApp] JupyterLab application directory is /opt/conda/share/jupyter/lab
|
||||
# [I 01:14:50.754 NotebookApp] Serving notebooks from local directory: /home/jovyan
|
||||
# [I 01:14:50.754 NotebookApp] 0 active kernels
|
||||
# [I 01:14:50.754 NotebookApp] The Jupyter Notebook is running at:
|
||||
# [I 01:14:50.754 NotebookApp] http://[all ip addresses on your system]:8888/?token=04646d5c5e928da75842cd318d4a3c5aa1f942fc5964323a
|
||||
# [I 01:14:50.754 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
|
||||
# [C 01:14:50.755 NotebookApp]
|
||||
|
||||
# Copy/paste this URL into your browser when you connect for the first time,
|
||||
# to login with a token:
|
||||
# http://localhost:8888/?token=04646d5c5e928da75842cd318d4a3c5aa1f942fc5964323a
|
||||
```
|
||||
|
||||
Open your browser on the URL displayed, and you will find the notebooks from the Git repository and can work with them.
|
||||
|
||||
Reference in New Issue
Block a user