Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Take a small app (a web server, API, or script) and containerize it: write a Dockerfile (correct base image, COPY, dependency install, a proper CMD/ENTRYPOINT, EXPOSE), add a .dockerignore, build a tagged image, and run it with a published port so it's reachable on the host. The image must build reproducibly and the container must actually serve.
Builds cleanly; correct base, dependency install, and CMD/ENTRYPOINT; the container runs and serves.
A .dockerignore excludes junk; the build context is lean; the image is tagged sensibly (not bare :latest reliance).
Container is started with a published port (-p) and is actually reachable on the host; logs are visible.
Dockerfile is readable and ordered so the dependency layer caches across code changes.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Containerize an application with a Dockerfile ## Goal Take a small app (a web server, API, or script) and containerize it: write a Dockerfile (correct base image, COPY, dependency install, a proper CMD/ENTRYPOINT, EXPOSE), add a .dockerignore, build a tagged image, and run it with a published port so it's reachable on the host. The image must build reproducibly and the container must actually serve. ## Acceptance criteria - [ ] Working Dockerfile: Builds cleanly; correct base, dependency install, and CMD/ENTRYPOINT; the container runs and serves. - [ ] Build hygiene: A .dockerignore excludes junk; the build context is lean; the image is tagged sensibly (not bare :latest reliance). - [ ] Run & reach it: Container is started with a published port (-p) and is actually reachable on the host; logs are visible. - [ ] Clarity: Dockerfile is readable and ordered so the dependency layer caches across code changes. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.