The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
```
```
docker run -it --rm jupyter/minimal-notebook start.sh ipython
docker run -it --rm jupyter/all-spark-notebook start.sh ipython
```
```
Or, to run JupyterLab instead of the classic notebook, run the following:
Or, to run JupyterLab instead of the classic notebook, run the following:
```
```
docker run -it --rm -p 8888:8888 jupyter/minimal-notebook start.sh jupyter lab
docker run -it --rm -p 8888:8888 jupyter/all-spark-notebook start.sh jupyter lab
```
```
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
```
```
docker run -it --rm jupyter/minimal-notebook start.sh ipython
docker run -it --rm jupyter/base-notebook start.sh ipython
```
```
Or, to run JupyterLab instead of the classic notebook, run the following:
Or, to run JupyterLab instead of the classic notebook, run the following:
```
```
docker run -it --rm -p 8888:8888 jupyter/minimal-notebook start.sh jupyter lab
docker run -it --rm -p 8888:8888 jupyter/base-notebook start.sh jupyter lab
```
```
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
```
```
docker run -it --rm jupyter/minimal-notebook start.sh ipython
docker run -it --rm jupyter/datascience-notebook start.sh ipython
```
```
Or, to run JupyterLab instead of the classic notebook, run the following:
Or, to run JupyterLab instead of the classic notebook, run the following:
```
```
docker run -it --rm -p 8888:8888 jupyter/minimal-notebook start.sh jupyter lab
docker run -it --rm -p 8888:8888 jupyter/datascience-notebook start.sh jupyter lab
```
```
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
```
```
docker run -it --rm jupyter/minimal-notebook start.sh ipython
docker run -it --rm jupyter/pyspark-notebook start.sh ipython
```
```
Or, to run JupyterLab instead of the classic notebook, run the following:
Or, to run JupyterLab instead of the classic notebook, run the following:
```
```
docker run -it --rm -p 8888:8888 jupyter/minimal-notebook start.sh jupyter lab
docker run -it --rm -p 8888:8888 jupyter/pyspark-notebook start.sh jupyter lab
```
```
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
```
```
docker run -it --rm jupyter/minimal-notebook start.sh ipython
docker run -it --rm jupyter/r-notebook start.sh ipython
```
```
Or, to run JupyterLab instead of the classic notebook, run the following:
Or, to run JupyterLab instead of the classic notebook, run the following:
```
```
docker run -it --rm -p 8888:8888 jupyter/minimal-notebook start.sh jupyter lab
docker run -it --rm -p 8888:8888 jupyter/r-notebook start.sh jupyter lab
```
```
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
```
```
docker run -it --rm jupyter/minimal-notebook start.sh ipython
docker run -it --rm jupyter/scipy-notebook start.sh ipython
```
```
Or, to run JupyterLab instead of the classic notebook, run the following:
Or, to run JupyterLab instead of the classic notebook, run the following:
```
```
docker run -it --rm -p 8888:8888 jupyter/minimal-notebook start.sh jupyter lab
docker run -it --rm -p 8888:8888 jupyter/scipy-notebook start.sh jupyter lab
```
```
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
The `start.sh` script supports the same features as the default `start-notebook.sh` script (e.g., `GRANT_SUDO`), but allows you to specify an arbitrary command to execute. For example, to run the text-based `ipython` console in a container, do the following:
```
```
docker run -it --rm jupyter/minimal-notebook start.sh ipython
docker run -it --rm jupyter/tensorflow-notebook start.sh ipython
```
```
Or, to run JupyterLab instead of the classic notebook, run the following:
Or, to run JupyterLab instead of the classic notebook, run the following:
```
```
docker run -it --rm -p 8888:8888 jupyter/minimal-notebook start.sh jupyter lab
docker run -it --rm -p 8888:8888 jupyter/tensorflow-notebook start.sh jupyter lab
```
```
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
This script is particularly useful when you derive a new Dockerfile from this image and install additional Jupyter applications with subcommands like `jupyter console`, `jupyter kernelgateway`, etc.
