Releases: omegaup/omegajail
Releases · omegaup/omegajail
v3.6.0
Install the Python packages from the Dockerfile #minor (#15) The Dockerfile is now the canonical way to set up the system to run mkroot. mkroot's job is _only_ to copy stuff from the real / to the rootfs, so it shouldn't be installing stuff itself.
v3.5.0
Refactor how the Docker images are built #minor (#14) It turns out that since Docker images are additive, and the runtime container was depending on the container that runs mkroot, and that generates _tons_ of files, the resulting container ended up having ~2x the number of files, just to be deleted immediately in the runtime container. This caused zero disk savings. Now the container that runs mkroot is a completely separate one, so there's no duplication in the runtime container!
v3.4.0
Add a way to preserve stdio #minor This change makes it possible to use stdio across the compiler. It's only enabled with --disable-sandboxing, because that might leak a file descriptor that was open outside of the container, defeating the whole purpose.
v3.3.0
Refactor how the JavaScript files are obtained #minor (#12) This change moves the JavaScript file obtention to the Dockerfile. This simplifies mkroot a bit and makes it possible to run npm later to install stuff.
v3.2.0
Improve release process (#11) We almost never want to not bump the version, since rebase merges are possible. Also, since the omegaup package was introduced, we need a new container, so this is a #minor release.
v3.1.0
Install libkarel from PyPI (#9) This change uses the PyPI wheel instead of just copying the .py file from GitHub. #minor
v3.0.1
Build using C++20 This change adds the --std=c++2a flag to start building stuff with C++20.
v3.0.0
Add the `--disable-sandboxing` flag #major This change adds the `--disable-sandboxing` flag to omegajail. This is very dangerous to use, but it's also the only way one can run omegajail while inside a Docker container, without requiring such container to run unprivileged.
v2.0.0
Add standalone versions of the grader and runner This change includes a standalone version of the grader and runner. Its main use is going to be to compare the differences in behavior or an old rootfs and a new one.
v1.0.3
This is the last release that uses the Bionic container.