Kattis in a Container

The same ICPC test/run/build configuration that kattis.com uses for problem solvers and problem makers.

If want to practice for or contribute to the ICPC regional contests which runs on kattis, then you need to make sure your code builds and runs as expected. This project makes that easy using containers running on docker.

intro video

Problem Solver

Welcome! Use the --slim setup option below. You don't need the validator or latex tools. Only the -slim and -web tests should pass with tests/all.

Problem Contributor

Thanks! Use the --fat (default) option below. You do need the validator and latex tools. All the tests should pass with tests/all.

Setup

Step 0 - Docker Toolbox

You need Docker Toolbox (win|mac). Or docker CE in linux. Docker CE is a poor experience in windows, so don't do that.

I assume you are running all commands from a terminal (mac/linux) or a Docker CLI bash shell in windows. Basically echo $(pwd) and docker ps should work.

Step 1 - Download (tar|zip), fork or clone this repository.

• Clone is a pretty good option, because then it's easy to update later with git pull
• Fork is a pretty good option if you are a chief judge getting ready to make a new problem set for a contest, and want to make it easy to test for you and other judges.
• Download is simple.

Step 2 - Setup

In the root of this project directory in the docker shell from step 0, run setup.

• bin/setup Full pulled setup (prebuilt downloads from docker hub)
• bin/setup --build Build the containers locally. Useful if you want a tweaked container. Be patient.
• bin/setup --slim Skip the fat container verification container (latex + compilers + problemtools) just have the slim (gcc, java, etc.) containers for the languages to compile and run code.

You can redo this step as often as you want, but once per dev system should be enough unless there are updates to incorporate, like from a git pull of this repository.

Use

After setup, NOTICE THE DOT . context in project will set your path, while . uncontext resets it.

After setting the context, the dev tools,

cmake, make,g++,gcc,java,javac,python,python3, kotlin, kotlinc

run in containers using the kattis version of these languages. The default fat kattis setup (no --slim setup) also provides latex and problem verification tools:

pdflatex,problem2pdf,problem2html, verifyproblem

You can run commands directly in a container as follows (for example, to execute a compiled target) with:

kattis-docker command args... # fat container (no --slim setup)
gcc-docker command args... # gcc/g++/make/cmake
java-docker command args... # java/kotlin
python-docker command args... # python/pypy
python3-docker command args... # python3

There is a basic Makefile in tests/compile you can use as well, in that directory,

make gcc-test
gcc-docker ./gcc-test

will compile and run using the kattis toolchain. After setting your . context you should be able to copy the makefile to your build directory and just use it for building and testing single source file submissions.

Time

Launching the docker adds time (about 1 second on my system) that is not part of time limit when officially judged, so time inside the container:

gcc-docker time ./gcc-test

Tests

After setup,

tests/all

should pass all tests (except the *-kattis tests with the slim setup).

Dev (devlopers of these tools, not users of these tools)

To set this up for dev/testing on ubuntu 18.04:

Setup docker: https://docs.docker.com/install/linux/docker-ce/ubuntu/

Add the current user to the docker group:

sudo usermod -a -G docker $USER

If you want to run some tests:

tests/all --dryrun=false --pattern='.*' --issues=false

If you want a full test

bin/clone-build-test --branch=master --tmp='' --keep=false

If you want to run automatic tests:

sudo cp bin/kattis-docker-cron /etc/cron.weekly