https://github.com/bast/teaching-setup
Containerized teaching setup which creates an isolated configurable shell.
https://github.com/bast/teaching-setup
apptainer teaching
Last synced: 26 days ago
JSON representation
Containerized teaching setup which creates an isolated configurable shell.
- Host: GitHub
- URL: https://github.com/bast/teaching-setup
- Owner: bast
- License: mit
- Created: 2024-08-25T15:33:40.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2024-08-27T08:16:35.000Z (about 1 year ago)
- Last Synced: 2025-01-28T02:32:36.663Z (8 months ago)
- Topics: apptainer, teaching
- Language: Shell
- Homepage:
- Size: 6.84 KB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# teaching-setup
**Containerized teaching setup which creates an isolated configurable shell.**
This can be useful for the following situation:
- You want to teach a course about shell/ command line tools.
- Your Linux environment is heavily customized and you don't want to change it
but at the same time it does not help beginners to see an environment which is
different from what they have.
- Your Linux distribution is very different from what your students have and therefore
it does not help you to create a new user account on your machine to teach from there.
- You want to have a clean environment for teaching.
- You want to create the illusion of teaching from an Ubuntu-like environment.
- It creates an isolated home folder: Nobody sees your messy home folder and you cannot mess up more.
## Requires
- [Apptainer](https://apptainer.org/)
## Usage
- Clone this repository.
- Launch: `./run.sh`
- This starts a new terminal and creates a home folder in the place where you run the script.
## Design decisions
- Why are some settings outside the container? Why do I need to build the container? Why is not all just baked into the container?
- Later I might do that and build a container image on GitHub but for now it
makes it easier to tweak settings without rebuilding the container.
## Ideas for what to add into it
- Sharing the history of commands, maybe using https://github.com/bast/history-window/.
- More tools depending on the course.
## Inspiration
- https://blog.yadutaf.fr/2017/09/10/running-a-graphical-app-in-a-docker-container-on-a-remote-server/
- https://blog.jessfraz.com/post/docker-containers-on-the-desktop/