Tutor VS runlike

I don't know Open EDX but it looks like Tutor is a separate distribution of it for Docker: https://docs.tutor.overhang.io

I'm not an ops guy, but I know it was a constant source of trouble in our team and a large challenge to keep it running smoothly. For us it took 2-3 experienced engineers something like 2 years to have a stable and smoothly running production environment at scale.

If you start from scratch today things may have gotten better. You might want to look at https://github.com/overhangio/tutor, I know Régis has been hard at work making it easier to run Open edX.

Shameless self-plug: I am the principal maintainer of Tutor, the Docker-based Open edX distribution designed for peace of mind. Open edX is the free, open source software that powers some of the most popular online learning platforms in the world, such as edX.org, openlearning.mit.edu, the national education platform of France, Guatemala, Greece, and many others.

Have you considered extending an existing online learning system? Open edX is written in Django for instance. You could try it out here: https://docs.tutor.overhang.io

You can use this tool to figure out how to run again any currently running container https://github.com/lavie/runlike

Issue for podman support: https://github.com/lavie/runlike/issues/71

I had started out the same way, especially if it was a new app and I wasn't familiar with how I really wanted to run it. Some containers expect a fair number of environment variables and multiple mounts. Once I got everything working, I would create a script /svcs with the corresponding docker run command. There's even a cool tool called "runlike" which can create a well formatted command for any running container.

https://github.com/lavie/runlike/

But I've got those migrated to docker-compose files these days and I try to start with the docker-compose file instead of going directly into testing out docker run commands.