Digital Mine on OpenEgiz

Judge Environment

Each Submission runs in a separate virtual machine created from a single base image and destroyed after evaluation. The environment contains no data from other Submissions and no access keys or accounts of the Organizer (Rules, clause 6.4). The specifications below let you reproduce the environment and test the README.md instructions before the Freeze.

Specifications

Architecture amd64 (x86-64), KVM virtual machine
CPU 8 vCPU
RAM 16 GiB
Disk 60 GB, of which about 55 GB free
Operating system Ubuntu 24.04.5 LTS (official cloud image), kernel 6.8
Docker Docker Engine 29.1.3, Docker Compose 2.40.3, Buildx 0.30.1 (from the Ubuntu repository)
Preinstalled software only the contents of the cloud image (git, curl, python3, etc.) and Docker. The make utility is not installed; any required software is installed by the README.md instructions (for example, sudo apt install -y make)
User judge, member of the docker group, passwordless sudo
Start-up time limit 75 minutes

Network

User interface

The Submission's interface is opened in a browser with the same network policy as the Submission:

Testing the instructions

Any computer or virtual machine with Ubuntu 24.04 amd64, 8 CPUs, 16 GB of RAM and 60 GB of disk space, with Docker Engine 29.1 and Docker Compose 2.40 installed and no other software, is suitable for testing. Example of creating such a virtual machine:

multipass launch 24.04 --cpus 8 --memory 16G --disk 60G --name judge
multipass shell judge
sudo apt-get update && sudo apt-get install -y docker.io docker-compose-v2 docker-buildx
sudo usermod -aG docker "$USER" && newgrp docker

Then clone the Team Repository and follow the README.md instructions exactly as written. Anything that works only because of your own computer's setup (installed programs, environment variables, downloaded images, files outside the repository) will not work in the Judge Environment.