TLJH on EC2 breaks shortly with 404

Here’s a revised version of your message:

I successfully got Docker Compose working with The Littlest JupyterHub (TLJH), set up a Cloudflare Tunnel, and even managed to mount a folder and access it. Initially, everything worked well.

However, the setup didn’t last. The TLJH container started behaving unpredictably, and now every rebuild of the image results in a 404 error. After some research, I understand this might be due to systemd compatibility issues between Docker and TLJH.

I’m wondering: is there a better approach to achieve my goal, or should I just install JupyterHub directly on my instance without using Docker?

Here’s what I’m trying to achieve:

I have an app that generates md files for my users, and I want to provide users access to a Jupyter editor where they can edit those files that is only for them to access. My initial plan was to generate a unique URL for each file that users could log into. For minute it was working perfectly However, I’ve read that using TLJH in Docker containers is not recommended, and now I’m uncertain how to proceed.

Any advice or recommendations would be greatly appreciated!

Let me know if you’d like further refinements!

Yepp tljh is meant to be installed directly on the VM running ubuntu or debian, not encapsulated inside a container.

2 Likes