Master Docker & Containers: Hands-On DevOps Training

Determine the system requirements for a Docker host, including a 64‑bit processor with VT‑x or AMD‑v and at least 4 GB RAM. Enable BIOS virtualization for Windows, macOS, or Linux.

Set up a docker host on an ubuntu EC2 instance using the ubuntu repository install, enable the docker service, and grant the ubuntu user docker access.

Learn how to install Docker from the official Docker registry on an Ubuntu VM, verify the latest version, and configure a production-ready Docker host in AWS.

Interact with a docker host using the docker cli to manage images, containers, networks, and volumes through the docker daemon, following the docker object action command hierarchy.

Discover how Docker images serve as blueprints for containers, and learn to pull and push images from Docker Hub using tags like latest and 20.04.

Create custom docker images tailored to specific libraries, versions, and settings, then automate builds with a dockerfile to streamline CI/CD and secure image management.

Push images to Docker Hub, private registries, or cloud registries to enable collaboration and secure distribution for corporate environments, with future labs on ci/cd integration.

Explore Docker image management by pushing and pulling images to registries, listing and inspecting images, tagging for version control, and removing unused images from the host.

Master two Docker container creation methods—imperative for quick, one-off experiments and declarative using a Dockerfile for customizable, repeatable images with version control.

Master the imperative method to create docker containers, pull nginx, enable an interactive bash session, and manage containers with --name, docker start, docker attach, and ctrl-p ctrl-q detach.

Create a docker container imperatively with docker run, port 80 mapping, and ubuntu latest running apache2, then verify access via the AWS host after starting the service.

Master the declarative method to build containers by creating a docker file, building its image, and launching a container, using from, run, copy, expose, and cmd commands.

Explore docker networking, enabling container communication within and across hosts, cover drivers and modes, and verify connectivity with ifconfig and ping while building a reusable net image with networking utilities.

Explore Docker bridging by observing how the default bridge connects containers on a single host, enabling inter-container communication through IPs like 172.17.0.2 and 172.17.0.3.

Learn to create and manage user defined Docker bridge networks, assign custom subnets, enable DNS-based container communication, and dynamically attach or detach containers for improved isolation.

Publish ports to expose a container to the outside world by mapping host ports to container ports with docker run -p. Use distinct host ports for each container.

Explore docker host networking, where a container shares the host network for direct, high‑performance access. Note its Linux exclusivity and port conflict limitations, not supported on Mac or Windows.

Learn how overlay network creates a distributed, multi-host Docker network that enables container communication across hosts, requires swarm service, and is planned after completing swarm setup.

Learn macvlan, a Docker network that lets containers obtain external network IPs and directly communicate, bypassing the Docker host network.

Explore how Docker's none networking mode isolates containers, contrasting it with the default bridge and swarm limitations to boost security in container deployments.

Explore how docker network plugins extend default networking beyond host, macvlan, overlay, and bridge modes by adding third‑party capabilities and enabling Cisco ACI integration.

Learn how Docker storage enables persistent data beyond containers using volumes, bind mounts, and tmpfs, while data stored outside the container remains accessible.

Explore how Docker volumes store data permanently by mounting volumes to containers. Attach, inspect, and share volumes across containers for persistent storage.

Learn how docker bind mounts let you mount a host directory into a container to share data across containers and persist it beyond container life.

Learn how Docker tmpfs creates a temporary in-memory storage by mounting data in the host ram for each container, offering fast, non-persistent storage that is not shared across containers.

Learn how multi-stage builds in docker separate build and deployment stages, using multi-stage docker files to create reproducible images and streamlined, secure production environments.

Install a Java-based Spring Boot application on an Ubuntu 20.04 AWS VM, transfer files with scp, build with mvn clean install, and run on port 8080.

Demonstrate installing the same application in a container with a standard Dockerfile through a four-stage process, including copying pom.xml and src, installing OpenJDK and Maven, and exposing port 8080.

Compare standard docker file with multi-stage docker file for building lean production images. See how multi-stage splits build and deployment, reduces image size, and improves security by copying only essentials.

Explore building and running a Spring Boot app with a multi-stage Dockerfile, using Maven and OpenJDK in build, and jar deployment in runtime.

Explore docker compose as a smart, YAML-driven tool to define and manage multi-container, multi-tier applications for DevOps automation, deploying services, networks, and volumes with a single file.

Discover how Docker Compose simplifies multi-container deployments with a single yaml file, automatically handling containers, networking, and volumes. Compare manual setup to one-file deployment for consistent, portable environments.

Set up a docker host on an ubuntu 24.04 vm, install docker and git, and clone the demo application's source code to explore a multi-container setup without docker compose.

Set up a Docker host by provisioning an Ubuntu 20.04/24.04 LTS VM, install Docker and Git, and clone the source code from a Git repository.

Clone the multi-container docker app from the GitLab repo, log in as root, navigate to the docker compose directory, and prepare the MySQL and PHP web server containers.

Create a bridge network named my network to enable inter-container communication for a multi-container web app, verify with docker network ls, and prepare for deployment.

Create a MySQL container from a Dockerfile to set up Testdb with init SQL, including a users table and root password, then run with a persistent volume.

Pull and run the adminer container without a dockerfile, link it to the db container, and map host port 8081 to the container's 8080 for web access.

Create a php web container from a php 7.4 apache image, install pdo and pdo_mysql, copy app files to /var/www/html, and test the multi-container setup before moving to docker compose.

Clean up an existing docker host by stopping and removing all containers, networks, volumes, and images, then prepare for deploying a multi-container application with docker compose.

Set up the Docker host to use Docker Compose, verify installation, install by downloading binaries and granting executable permissions, and prepare the GitLab repository for the multi-container web application.

Discover how docker compose defines and runs a multi-container application with a docker-compose.yml, configuring services, volumes, and networks, and using build context to assemble images.

Define services in a docker-compose.yml to configure a multi-container app with images, ports, volumes, and environment variables. Use docker compose up, down, logs, and exec to manage and run containers.

Explore a docker-compose.yml file, including version 3.7, three services web, db, and adminer, with a local build context, ports, network, and depends_on sequencing.

Explore the db service in a docker compose file, building from the MySQL folder, initializing with init.sql to create a users table, and configuring root password, testdb, volumes, and network.

Configure a docker compose adminer service using the official adminer image, with restart always, host port 8081 to container 8080, and a bridge network plus a persistent MySQL data volume.

Learn to create a Docker Compose file on the host, start containers in detached mode, and verify networks, volumes, and ports for a multi-container app (8080 app, 8081 admin).

Learn to deploy and manage scalable, highly available container environments across multiple docker hosts using container orchestration with docker swarm and kubernetes, including auto scaling, load balancing, and self-healing.

Explore Docker Swarm, Docker's built-in container orchestration that manages a cluster of Docker engines as a single system for high availability and simple scaling.

Explore Docker swarm terminologies, including swarm, node, manager and worker roles, the leader among managers, service types (replicated and global), tasks, stacks, and overlay and ingress networks for high-availability deployments.

Set up a basic Docker swarm on AWS EC2 with one manager and two workers, following seven steps to run and verify a service, with high availability planned later.

Install docker on three ubuntu machines (manager and two workers) using commands, verify with docker version and systemctl status docker, and enable the ubuntu user to run docker without root.

Set up a three-node swarm on Ubuntu 24.04 in AWS EC2, open swarm ports 2377, 7946, 4789, and assign a manager and two workers, preparing for Docker installation.

Initialize Docker swarm on the manager node, obtain the join token, enroll workers, then verify the cluster with docker node ls to confirm a ready swarm.

Deploy a three-replica nginx service in a docker swarm, verify with docker service ls and docker service ps, and access the service via port 80 across manager and worker nodes.

Set up a Docker Swarm cluster with high availability and fault tolerance to keep applications running during node failures by distributing workloads across manager and worker nodes to maximize uptime.

Explore how raft consensus enables high availability in docker swarm by coordinating leader election, quorum-based decisions, and log replication among manager and worker nodes.

Explaining raft consensus best practices, this video emphasizes that two manager nodes cannot provide high availability; use at least three managers to form a majority and elect a leader.

Apply raft consensus best practices to ensure high availability in docker swarm. Avoid even-numbered manager nodes to prevent split-brain and rely on odd counts for clear majority.

Create five Ubuntu EC2 instances and configure a security group with cluster management (2377), node communication (7946), and overlay network (4789) ports to build a highly available Docker Swarm cluster.

Install Docker on five EC2 hosts to create a high-availability swarm, using SSH with Ubuntu user, avoid root, and prepare for running commands across hosts with a configuration management tool.

Set up a minimal Docker swarm with one manager and two workers, initialize the swarm, deploy an nginx service, and analyze how manager failure creates a single point of failure.

Extend the Docker swarm with two manager nodes and three workers, then deploy a five-replica nginx service and test quorum and leadership failover.

Expand Docker Swarm cluster to three manager nodes and two or more workers to boost high availability and quorum; promote a worker to manager and deploy a five-replica nginx service.

Configure a three-manager high-availability docker swarm with two workers, dedicate a manager to orchestration by draining it, and verify task distribution with docker service ps.