Quick start
From git clone to your first check
You need Git, Docker and a terminal. Or skip local setup and open the lab in Codespaces.
1. Get the lab
git clone https://github.com/Ali-Shaikh/docker-practical-lab.git
cd docker-practical-labZero-install alternative: open the repo in GitHub Codespaces and run the same commands in the browser terminal.
2. Run the pre-flight check
doctor checks Docker, Compose, BuildKit, free disk and the lab port range before anything starts.
./lab doctor.\lab.ps1 doctor3. Start the baseline
up creates the labelled dpl-net network and pulls shared official base images when they are missing. The first run may take a few minutes; later runs are quick.
./lab up
./lab status.\lab.ps1 up
.\lab.ps1 status4. Run a sample app on the host first
Before any Dockerfile, prove the app works natively. The Python API is a good first stop:
cd apps/python-api
python -m venv .venv
# follow apps/python-api/README.md5. Complete exercise 01 and mark it
Open exercises/01_run-inspect.md, follow the brief, then self-check:
./lab check 01.\lab.ps1 check 016. Try a break-and-fix drill
After a few exercises, list the six drills and start with crash-loop. Read the brief under drills/crash-loop/brief.md, repair the failure, then verify.
./lab drills
./lab break crash-loop
./lab verify crash-loopOnly one drill is active at a time. ./lab reset clears drill state and labelled lab junk when you want a clean slate.
Where next
Work through exercises 02-10 with ./lab check NN. When something looks wrong on the host, start with ./lab doctor and ./lab status. Safety and cost questions live in the FAQ.