Up to 70% Off for Students & Emerging Markets - Apply Now

Contribute: All Guides
Docker

Submitting a Docker Lab

Send the source code and Dockerfile as one password-protected zip. We build the image and put it on the platform.

A Docker lab is a containerised app or service that learners attack from the browser-based AttackBox or over the VPN. You send us the source code and Dockerfile as one password-protected .zip, uploaded from your CyLynk dashboard. Our team builds the image, sets it up on the platform and writes the final learner instructions from what you provide.

You don't need a registry, Docker Hub, GitHub access, AWS or any infrastructure of your own.

How It Works

  1. Apply to contribute. Go to Contribute on the CyLynk website and select Apply to contribute. We review applications and you'll get an email when you're approved.
  2. Build and test the lab locally so it meets the requirements below.
  3. Pack it into one .zip protected with the password Hck4G00d.
  4. Create the lab in your dashboard (My Dashboard → Contribute → New Docker lab), paste your README and upload the zip.
  5. Submit it for review. A reviewer approves it, asks for changes or declines it. You're notified at each step.
  6. We build it and publish it. You're notified when it goes live.

The Contribute page on the CyLynk website

The application form

1. Platform Requirements

The lab has to run on our platform without changes. Check each requirement before you submit.

Requirement What we need
Architecture The image must build for linux/amd64. On Apple Silicon or another ARM machine, build with --platform linux/amd64 to test.
One port The app listens on one TCP port, and that's the port learners reach. They reach it on a different port that we assign for each session, so don't hard-code a hostname or port in links, redirects or config. Use relative links. If learners need a second port, tell us before you submit.
Startup The container starts on its own, with no interactive setup. A session shows as ready once your app accepts connections on its port. If you give a health path (such as /health), we wait for it to respond instead.
Self-contained Put the app and everything it needs in one image where you can. Multi-container labs (for example app + database) are limited and must be agreed with us first.
No special privileges No privileged mode, extra Linux capabilities (such as NET_ADMIN or NET_RAW), host mounts or host networking. We can't enable them.
Resources Design for 0.5 CPU and 512 MiB of memory. If the lab needs more, say how much in the README.
Internet access Labs have no internet access by default. If yours genuinely needs it, explain why in the README.
Fresh every session Each learner gets a new container, and nothing is kept between sessions.
Configuration Environment variables must be fixed, safe example values. We can't inject secrets, so don't rely on them.

Test it like this before you submit:

docker build --platform linux/amd64 -t my-lab:1.0.0 .
docker run --rm -p 18080:<container-port> my-lab:1.0.0

Use a host port that differs from the container port, as above, and check that the app loads at http://localhost:18080 and that links, redirects and logins all still work. Then solve every flag yourself from a fresh container.

2. Security and Content Rules

The lab may contain a deliberate teaching vulnerability. It must not:

  • phone home, exfiltrate data, mine cryptocurrency or contact any outside server
  • contain real malware, unintended backdoors, real credentials, API keys, private keys or anyone's personal data
  • include code, images or data you don't have permission to share
  • attack anything outside its own container

Use throwaway credentials made for the lab only. If the scenario needs unusual network behaviour, such as simulated command-and-control, ask us before you build it.

3. What Goes in the Zip

my-lab.zip   (password: Hck4G00d)
└── my-lab/
    ├── LEARNER.md      the scenario and instructions learners follow
    ├── flags.md        every question, its answer, points and an optional hint
    ├── solution.md     a walkthrough showing how each flag is reached
    └── lab/
        ├── Dockerfile
        ├── (all source code, dependency and lock files, config, seed data)
        └── .env.example   if the app uses environment variables
  • lab/ must build with a plain docker build --platform linux/amd64 . from inside the folder. Include every file the build needs.
  • Don't include built images (docker save output), node_modules, virtual environments, build output or .git folders. We build from your source.
  • flags.md lists the questions in the order learners answer them. For each one, give the exact answer, the points and an optional hint. Flags use the CyLynk format Lynk{...}, for example Lynk{j3nk1ns_scr1pt_c0ns0le}. Learners never see this file.
  • LEARNER.md is what learners read: the scenario, what to find and any throwaway login details they need.

4. Create the Password-Protected Zip

Every lab archive uses the same password: Hck4G00d.

Why a password? Labs contain deliberately vulnerable code, and antivirus or email filters often delete or quarantine it in transit. The password keeps those tools out. It isn't a secret, so it doesn't protect anything sensitive. Never put real credentials in a lab.

Windows (7-Zip): right-click the my-lab folder → 7-Zip → Add to archive…. Set Archive format to zip, enter Hck4G00d as the password, set Encryption method to AES-256 and select OK.

macOS (Keka): set the format to ZIP, enable Encrypt and enter Hck4G00d, then drag the folder onto Keka. Or use Terminal:

zip -er my-lab.zip my-lab/     # enter Hck4G00d when prompted

Linux or macOS (7-Zip command line):

7z a -tzip -pHck4G00d -mem=AES256 my-lab.zip my-lab/
7z t -pHck4G00d my-lab.zip      # check it opens with the password

Before uploading, check that the zip opens with Hck4G00d and contains everything listed above.

5. Write Your README

The README is pasted into the form, not uploaded, so reviewers can read it without downloading anything. Include:

Section What to write
About Lab name, a short description, difficulty (Easy, Medium, Hard or Insane), estimated time, and what learners will learn
Port The one port learners use, plus any other port the app listens on and why
Health path A path that responds once the app is ready (such as /health), if there is one, and the expected start-up time
Environment variables Names, purpose and the safe values to use
Resources Whether 0.5 CPU / 512 MiB is enough, and if not, what it needs
Internet access Whether the lab needs it and why (the default is none)
Credentials Any throwaway logins learners or we need
Test steps How we can check it works, and what we should see
Known issues Start-up delays, limitations, anything unusual. Write "None" if there are none

6. Upload and Submit in Your Dashboard

  1. Go to My Dashboard → Contribute and select New Docker lab.

    Your Contribute area

  2. Enter a title and a two- or three-sentence summary, paste your README, then choose your zip and select Create and upload.

    Creating a Docker lab

  3. Keep the tab open while it uploads. If the upload is interrupted, open the lab again and choose the same file to resume where it stopped.

  4. When the upload finishes, select Submit for review. The lab is locked while it's in review.

    A lab ready to submit

Limits: up to 100 GB per file, 5 labs in progress at a time and 200 GB of uploads in total.

7. After You Submit

  • Changes requested: read the reviewer's feedback, fix the lab, upload a new zip if needed and submit again.
  • Approved: our team builds the image and sets up the lab. You don't need to do anything else.
  • Live: you're notified when learners can use it.
  • Declined: the reviewer explains why. A declined lab can't be resubmitted, but you can start a new one.

To update a live lab, create a new submission with the new version and say what changed in the summary.

Checklist

  • ☐ docker build --platform linux/amd64 . works from inside lab/
  • ☐ The app starts with no interactive setup and listens on one documented port
  • ☐ Links, redirects and logins work on a different host port
  • ☐ It runs in 0.5 CPU / 512 MiB, or the README says what it needs
  • ☐ No privileged mode, extra capabilities, host mounts or host networking
  • ☐ Every flag can be solved from a fresh container
  • ☐ No real secrets, personal data or content you can't share
  • ☐ The zip contains LEARNER.md, flags.md, solution.md and lab/
  • ☐ The zip is protected with Hck4G00d and opens correctly
  • ☐ The README is pasted into the form, the upload has finished, and the lab is submitted for review