Listed as Free on Udemy when checked on 5 November 2026. No coupon or subscription trial is required for the listed lessons. Enrollment needs a Udemy account; availability can change.
About this course
A container can make a small application easier to run in a second environment. Start by separating three questions: what goes into the image, what the container does when it starts, and what needs to stay available after the container is replaced. Docker gives each question a different place in the workflow.
Samarth Deyagond’s free beginner course uses short Dockerfile examples before moving to storage and networking. You should be comfortable with basic Linux commands and have a little networking knowledge. The course dates from 2019, so check current Docker documentation for installation, command options, and supported images as you follow the concepts.
| Official course | Docker for beginners |
|---|---|
| Created by | Samarth Deyagond |
| Platform | Udemy |
| Language | English |
| Level | Beginner |
| Listed duration | 77 minutes; 16 lectures across 3 sections |
| Completion terms | Not included with a new free enrollment |
What you’ll learn
The first section introduces Dockerfile instructions for building an image, choosing startup behavior, and adding metadata or configuration. Two lessons discuss persistent storage and mounts. The final section covers port declarations and container networking. The lessons total around 77 minutes and provide an introduction to the container workflow.
Skills you’ll gain
- Dockerfile instructions
- Image builds
- Container startup
- Persistent volumes
- Bind mounts
- Container networking
Separate build instructions from startup behavior
A useful first exercise is to build an image that prints a short message. Write down which instructions select the base image and which execute while Docker builds it. Then identify the instruction that supplies a default action when the container runs. Keeping build and startup separate helps you avoid adding a step to the image when you meant it to run each time a container starts.
After your first successful run, change one instruction and predict what you will see next. Try changing the startup message before adding more packages. Check the results against your prediction. Use a small example so you can trace each change to a single line. That habit helps when a bigger project produces a different result than expected. Give the image a practice tag you can identify later. When two versions behave differently, check which tag you ran and which Dockerfile you built from. This gives you two useful facts to record before you change anything else.
Decide what should survive a new container
For a separate storage exercise, write a harmless text file into a named volume and then use that same volume from a new container. Compare the outcome with a file written only into the first container’s writable layer. A volume has its own lifecycle, which is useful when you want to replace a container without losing practice data. Make a short note of the named volume and the container path you attached it to. Then repeat the read from another container without changing the image. If the file is missing, check the volume name and the mount target before deciding the data was lost.
A bind mount is different: it connects a path on the host to a path in the container. Try one using a disposable folder and only files you are comfortable exposing to the container. Check which side of the mount each path refers to before you run the command. Knowing where a file actually lives makes it easier to understand why changes can show up in both places.
Test access from the right place
For networking practice, use a local test service and decide who needs to reach it. Containers on the same Docker network can communicate without publishing a port to the host. If your browser on the host needs access, the port has to be published explicitly. A Dockerfile’s EXPOSE instruction documents a port and does not publish it by itself. Bind the practice service to a local interface where appropriate and check current guidance before exposing it beyond your machine.
Treat health status and process lifetime as separate ideas. A health check can report that a running service is unhealthy; it does not, by itself, stop the container. This distinction is useful when diagnosing a container that is still running but does not answer requests. Keep your first exercises local and use the course as a foundation before moving on to orchestration, release pipelines, or hardening services for production.
Related courses for your next step
- Add a related skillFree Bash Scripting Course
Focus: Script setup · Interpreter selection
Beginner
- Add a related skillFree Postman API Testing Course
Focus: HTTP request inspection · Response validation
Beginner
Compare course focus, level and study time
| Course | Level | Focus | Study time |
|---|---|---|---|
| This course — Free Docker Containers Course: Images, Storage, and Networking | Beginner | Dockerfile instructions · Image builds · Container startup | 77 minutes (Udemy listing) |
| Free Bash Scripting Course: Write Your First Linux Script | Beginner | Script setup · Interpreter selection · Shell builtins | 44 minutes (Udemy listing) |
| Free Postman API Testing Course: From Requests to Assertions | Beginner | HTTP request inspection · Response validation · Postman collections | 111 minutes (Udemy listing) |
Frequently asked questions
Do I need Linux experience?
The listing asks for Linux and networking basics.
Does EXPOSE publish a port?
No. It declares the intended container port. Publishing uses a separate runtime option.
Does the course cover production orchestration?
The public outline focuses on Dockerfiles, storage, and container networking fundamentals.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.