Feedback from testing https://twitter.com/Juan_Kinda_Guy

Yuvi,

I had a few minutes (OK an hour) this morning, so I decided to take a crack at installing TLJH. I’m copying Matt Craig and our IT folks on this so they have this as well. I’ll be gone next week, so this is my contribution to the effort for now.

I’ve downloaded the ubuntu-18.04-live-server ISO and installed a VM of it under Parallels on my Mac. I had some issues with the installation instructions.

Step 1 went fine and the installation script seemed to run without problems.

For "Step 2: Add admin user”, the instructions say to ‘open’ the /opt/tljh/config.yaml file. The file DOES not exist to start, the language was unclear. Should there have been a pre-existing YAML file or not?

Also, after trying to start the jupyter server using 'sudo systemctl restart jupyterhub’, there is no feedback (I know when I start a web server, normally I get a one line feedback that the server started. I don’t know if the server actually started or not. I suspect it didn’t start, but the instructions don’t provide a way to check if the server is running other than connecting to it, but it doesn’t specify the port to use to connect. Is there a default port? Sorry if this should be obvious…

Step 3 presented a bunch of issues. conda doesn’t appear to be in the default path for my admin user. Apparently my admin's bash profile was not modified during the install. Since the binaries were installed in /opt/tljh/user/bin, I modified my .profile to add that to my path and ran the conda configuration script by added this to the end of my .profile file

if [ -d "/opt/tljh/user/bin” ] ; then
    PATH="/opt/tljh/user/bin:$PATH
    . /opt/tljh/user/etc/profile.d/conda.sh
fi

However, despite the sudo -E (which is supposed to preserve the environment), it reported ‘command not found’. Looks like the directory conda is installed in is not considered safe for sudo (it is NOT listed in the secure_path variable in the default /etc/sudoers file). So I did a ‘sudo visudo’ to edit the /etc/sudoers file and added /opt/tljh/user/bin to the secure_path variable. (Actually, I see you addressed this sudo permission problem on the ‘Customizing User Environment’ page, by using the workaround

sudo PATH=${PATH} conda install -c conda-forge gdal

However, I figured I would bring it up, since I was just following the instructions when this happened).

At that point the following worked (I had a hiccup with a network disconnection, but rerunning the conda install command worked fine):

sudo -E conda install -c conda-forge gdal

However, when I did:

sudo -E pip install numpy

it said I had already installed it. I confirmed this by opening up an ipython shell and importing numpy

I still don’t know if I managed to get the installation working since I didn’t know how to access the Jupyter notebook server, but I hope this helps clarify possible installations issues from the point of view of a user.

Juan

jupyterhub / the-littlest-jupyterhub

Feedback from testing https://twitter.com/Juan_Kinda_Guy #8