Competition participant manual Preview

Your goal

Use the participant URL and team key supplied by the organizer. Keep the key private. You do not create a cloud platform or sign in as an organizer to join a prepared event.

Solve a problem in five steps

Sign in with your team's key.
Wait for the organizer to prepare the jobs and start the event.
Open an assigned problem and read its situation, first action and goal. For a new Docker event, choose Start / resume and wait until it is running.
Use its exercise URL, workbench, answer fields or AWS access as directed. Submit the complete flag or answer to the indicated checkpoint.
Read the verdict and score. Hints and wrong answers may change the score. Ask the organizer about an unavailable environment rather than repeatedly starting it.

Use Stop (keep data) to free active capacity. Resuming the same environment retains its writable layer and volumes, but not RAM. The host does not automatically evict or reset it. Defaults allow 3 active environments per team and 12 across the host, subject to the configured memory-cap budget. If a limit is reached, stop an environment you no longer need or contact the organizer. After make down / make local, new Docker jobs remain stopped until you resume them. Existing events keep their legacy lifecycle.

A real Docker/browser rehearsal verified PostgreSQL terminal access, three scored checkpoints, team isolation, and seven saved rows after stop/resume. This does not verify every one of the 15 terminal variants or every problem. A listed problem does not guarantee every interaction is ready.

Try the local event flow

If you are also organizing your own test, follow getting started: make local starts the same event/team system and make down stops it while preserving data. There is no separate individual-practice login or automatic progress reset.

Words you will see

Docker: A way to package an application and its dependencies so a matching practice environment can be recreated
Problem environment: the isolated application or cloud resources assigned to your team
Endpoint: the address of a service you open or register
Flag: the complete evidence string the problem asks you to submit
Hint: extra guidance; check its displayed cost before opening it

When something goes wrong

Give the organizer the problem name, visible error and time, without posting keys, flags or AWS credentials. Ending the event blocks new submissions and access issuance, but already issued AWS sessions may remain valid until they expire.