Docker and CI/CD Fundamentals
Proposed foundational DevOps course. Lab environments and any learner expenses will be documented before enrollment opens. Paid cloud resources are not promised.
- Linux
- Git
- Docker
- CI pipeline config
- Runbooks
This is fee-based Project-Based Training — not a paid internship. Registering interest is not enrollment and does not collect payment. Fee details will be shared before enrollment.
Program facts
- Duration
- 1 month
- Level
- Foundational
- Weekly commitment
- Approximately 8–12 hours per week (subject to final schedule)
- Delivery
- Online
- Availability
- Coming soon — interest registration available
- Fee
- Fee details will be shared before enrollment
- Mentor / supervisor
- Instructor or delivery owner assigned before open enrollment.
- Delivery owner
- Assigned before enrollment opens
- Certificate policy
- Certificate policy confirmed at enrollment open.
Paid cloud resources are not included unless explicitly published for an open cohort.
Audience, prerequisites, and selection
Audience
- Developers learning delivery automation
Prerequisites
- Basic Linux and Git
Curriculum
Curriculum status: forthcoming / proposed. Topics below are indicative and not a finalized enrollment curriculum until marked approved.
- Docker fundamentalsfoundational
- CI pipeline basicsfoundational
- Artifact and image hygienefoundational
- Deployment documentationfoundational
Learning outcomes
- Containerize a sample app
- Author a basic CI pipeline with checks
Project specification
Containerize a sample app and author a basic CI pipeline with checks and a runbook.
- Problem statement · Illustrative
- A sample application needs a repeatable container build and a CI pipeline that fails closed when checks fail.
- Primary user workflow · Illustrative
- Commit change → pipeline runs checks → image builds → pipeline status is visible → runbook explains how to run the image.
- Functional scope · Illustrative
- Dockerfile or equivalent, CI configuration, basic checks, image hygiene, and deployment documentation.
- Technical components · Illustrative
- Sample app, container definition, CI config, and runbook.
- Data requirements · Illustrative
- No production datasets. Secrets via environment variables only.
- Testing expectations · Illustrative
- Pipeline fails on a deliberate check failure and succeeds on the happy path.
- Known limitations · Illustrative
- Not a full multi-environment production platform. Paid cloud deploy targets are not assumed.
- What counts as completion · Illustrative
- Working pipeline, containerized sample app, and a short runbook.
Examples
- CI pipeline for a containerized sample application
Deliverables
- Dockerfile or equivalent
- Working CI pipeline
- Runbook / deployment notes
Example or assigned project work—not a published student achievement or employment guarantee. Student work is not assumed for commercial use without appropriate agreements. Sections marked illustrative are representative examples, not a fixed commercial brief.
Evaluation criteria
How work is reviewed — clarity of decisions matters as much as a working MVP.
- Working pipeline and runbook
Evaluation focuses on observable engineering evidence. Exact rubrics are published per program when approved.
01
Main workflow correctness
Does the primary user journey work as specified?
02
Code comprehension
Can the participant explain what the code does and why?
03
Architecture explanation
Are component boundaries and trade-offs articulated clearly?
04
Input validation
Are invalid inputs rejected or handled safely?
05
Testing
Are expected behavior and at least one failure mode checked?
06
Edge-case handling
Does the work account for realistic non-happy-path conditions?
07
Documentation
Can another engineer set up, run, and understand the MVP?
08
Demonstration
Is the working result shown with an honest account of limitations?
Frequently asked questions
Ready to build something real?
Choose a pathway, review a program, and register interest when enrollment opens.