base-notebook defines environment variables for the Conda install path and the
notebook user. However, in some instances, these locations were still hardcoded.
Let’s use the variables instead.
stacks easily usable with JupyterHub.
* pip install jupyterhub to gain access to the jupyterhub-singleuser
startup script, which starts a single-user instance of the Notebook
server
* Add shell script to wrap jupyterhub-singleuser script; use as
alternate Docker command
fixes#181
(c) Copyright IBM Corp. 2016
This is done to more explicitly track what version of Debian Jessie is
being used as a base image. It will also ensure that it is properly
updated on the VM even if we forget. This also should help CI and VM
builds stay speedy by using the cache even when there is a newer version
of Debian Jessie. In the long run, we may wish to re-evaluate this
strategy and fix our CI and deployment systems so as to be able to use
the latest version of Debian Jessie with important CVE and other fixes.
Bite the bullet and preinstall it so that plotting libs that default
to using desktop rendering just work (matplotlib, ggplot, ...)
out of the box without having to get configuration right beforehand
(e.g., %matplotlib inline ahead of matplotlib import)
Only adds ~100k to the image size
(c) Copyright IBM Corp. 2015
* Pass $@ args to start-notebook.sh
* Set tini as entrypoint, but keep start-notebook.sh as easily overridable CMD
* su to jovyan user within start-notebook.sh script
Contribution (c) Copyright IBM Corp. 2015
* Create user jovyan with UID=1000 in the default users group in the Dockerfile
* Set group ownership of user home and conda to root to avoid 'users' group from host access when mounted
* Set stick bit on both paths so root owns subdirs too
* Change jovyan UID if NB_UID is specified and is not the default 1000
Contribution (c) Copyright IBM Corp. 2015
* Only create jovyan and set perms if user does not exist
* Allow docker host mount for NB_WORK: copy skel files if useradd fails because home dir already exists
Contribution (c) Copyright IBM Corp. 2015
* Always remain as root during install
* Put kernel specs in system path, not user home
* Create user work directory at startup
* Note this is in 4.0 and up images, not 3.2
Contribution (c) Copyright IBM Corp. 2015
