loeper/stanford-cs212-pintos repository overview

⁠Docker Containers for Stanford's CS 212 (Winter 2021/22)

There are two container images for the CS 212 lecture:

1. loeper/stanford-cs212-pintos (this one): used to run an already compiled pintos kernel and tests
2. loeper/stanford-cs212-pintos-vscode-dev-environment: used to develop a custom pintos version as part of a devcontainer.json specification for vscode's Remote - Containers extension [more info]⁠

⁠Rationale

There are basically two options to run pintos: (a) compiling it on the development machine and (b) running the version provided on Stanford's myth and rice clusters.

In order to facilitate the former, we want to provide a dockerized environment that is as similar as possible to the one Stanford provides. Particurarly, it must be able to support multiple different (mainstream) architectures: amd64, arm64, armv7.

We meet those requirements by providing pre-built multi-arch docker container images via Docker Hub.

⁠Usage

For vscode usage instructions see: loeper/stanford-cs212-pintos-vscode-dev-environment⁠

If you want to use the non-IDE image, you can do the following:

1. Clone a fresh copy of the pintos source code base (or use your existing one instead; just keep in mind to change paths in that case though): git clone http://cs212.scs.stanford.edu/pintos.git ~/pintos
2. Start pintos inside the container to check if everything works as expected: docker run -v "$HOME/pintos:/pintos" -w "/pintos" --rm -it loeper/stanford-cs212-pintos pintos
   --> should display the pintos command line help
3. Drop a shell into the container and run everything you need to do, e.g. kernel compilation for threads and corresponding tests:
   docker run -v "$HOME/pintos:/pintos" -w "/pintos" --rm -it loeper/stanford-cs212-pintos:latest /bin/bash
   --> cd src/threads
   --> make
   --> cd build
   --> make check
   --> exit