polygott | Base Docker image for the Repl.it evaluation server | Continuous Deployment library

You can build either the entire image, a version that has a bundle of languages, and a version that is limited to a single language. The second one is used for CI, and the latter is recommended when you are adding or modifying support for a particular language, since building the entire image takes an extremely long time. Makefile targets are provided for each of these cases:. As you can see, there is a facility for testing that languages have been installed and configured correctly. This involves running commands which are specified in the languages' configuration files, and checking that the output is as expected. To debug, you can also use the make run and make run-LANG targets to launch shells within the images. You may want to bypass Docker's cache temporarily, for example to debug an intermittent network error while building one of the languages. To do this, identify the docker build command which is run by the Makefile, and run it yourself with the --no-cache flag. The CI requires having up-to-date generated artifacts (the files in out/) committed to ensure a consistent Docker build environment. These will be refreshed by running the tests, or by running make -B build/stamps/out).
The language configuration files are validated against a JSON Schema specification located in schema.json.
The .ejs files in the gen directory are transformed into shell scripts using the language configuration via the EJS templating system. This is done by a Node.js script inside the Docker image.
The multi-stage Dockerfile is created from the language configuration files.
Languages are installed in several phases. In phase 0, shared packages in packages.txt are installed, as well as APT keys and repositories are configured. In phase 1.0, apt-get update -y is run, which can be reused in later phases. In phase 1.5, language-specific packages are installed. In phase 2, language-specific setup commands are run.