- The start.sh script does different operations on users, and
sometimes one may need to do operations *after* that is done (as
opposed to /usr/local/bin/start-notebook.d/ which is run before).
This provides that possibility. (One use case is hooks which must
be run after the users are set up.)
- To be technically perfect, one might want to use something similar
to /usr/local/bin/pre-start-notebook.d/. But let's start with the
simplest thing possible for now - the expected use of this command
is only if people use NB_USER, etc in a way that requires small
follow up commands to be run.
- If notebook is running as root, this allows users to run arbitrary
commands pre-sudo. Consider security model.
- If NB_GID is set, it is likely that files created should have NB_GID
as their gid (if it doesn't matter, then this change is irrelevant.
If it does matter, the liklihood that 100 matches with what the user
wants is low).
- When NB_GID is set, create a new group with that gid. Then, set
this as the primary gid of the user. Set the user's supplemental
gids to NB_GID,100.
Adds the initial creation of the configuration file
jupyter_notebook_config.json to the image. This file
was missing as reported in issue #639 and caused an
error when trying to set a new password via the Web
interface.
Bumps the version of Jupyter Notebook to 5.6
Updates Apache Mirror URL because the current causes build timeouts
The mirror used now (mirrors.ukfast.co.uk) is fast enough and does not
point to an ad site and is already used in a different Dockerfile within
this repository.
Upgrade Ubuntu to latest LTS (Bionic 18.04), including:
- Change the IMAGE used for base-notebook;
- Keep Mesos install from Mesosphere's Xenial repository, since they
don't yet have a Bionic repository;
- gnupg needs to be installed for apt-key to work;
- --force-yes option to apt-get has been removed;
- Package libav-tools is replaced by ffmpeg;
- Update Let's Encrypt example script to use 18.04.
Only the top level permissions are set wrong due to kubernetes not being able to do this automatically.
This hits significant problems when the chown takes more than 30s and the pod fails to start
Update jupyterlab from 0.31 to 0.32.
Update the following extensions to matching versions:
- jupyterlab/hub-extension
- jupyter-widget/jupyterlab-manager
- jupyterlab_bokeh
