Gain insights into Docker fundamentals, delve into advanced concepts like database connectivity and Docker Compose, and discover how to monitor and scale services with Docker Swarm.

course_final_image.tar.gz

Flask App_new

docker-compose

Docker_build

flask_venv

Flask_demo_test

add db to container

Exercise

Exercise 2

exercise 3

exercise_4

Bonus Section - Flask

exercise 3-copy

docker-compose-copy

Docker_build-copy

add db to container-copy

Exercise 2-copy

exercise_4-copy

Bonus Section - Flask-copy

Docker_build-copy-copy

Whether you are a DevOps beginner or just a developer who wants to start working with containers, you’re in the right place. Docker is an in-demand technology that you will be exposed to frequently while on the job.

 

Docker is used for setting up, deploying, and running applications, at scale, by containerizing them. More on that later. Docker also provides developers with a consistent environment for product development, and along with Kubernetes, makes managing the development lifecycle a breeze.

 

In this course, you will learn the fundamentals of Docker such as containers, images, and commands. You’ll then progress to more advanced concepts like connecting to a database container and how to simplify workflows with Docker Compose. At the end, you’ll learn how to monitor clusters and scale Docker services with Swarm.

Working with Containers: Docker & Docker Compose


# Multiple Dockerfile use cases

There might be a situation where we need to have multiple Dockerfiles for different services.

Examples could be:
* Creating a microservices app
* Dockerfile for different environments such as development, production

In these cases, you have to tell docker-compose the Dockerfile it should consider for creating that specific service. 
> By default, docker-compose looks for a file named Dockerfile. Dockerfiles can have any name. It's just a file without any extension. We can override the default behaviour using `dockerfile:'custom-name'` directive inside the build section. 

# Implementation

Let's see this in action. We will add a new file called Dockerfile-db in the DB folder and make some changes in the docker-compose.yml file.

In the build section, we have
```
context: ./db
dockerfile: Dockerfile-db
```
`context`: Use this to specify the directory of Dockerfile or alternate Dockerfile relative to docker-compose.yml file

`dockerfile`: As mentioned in the note above, specify the name of alternate Dockerfile if it is not named as Dockerfile

Working with Multiple Dockerfiles

Introduction to Course

Why Docker?

Getting Started With Docker

Docker Fundamentals

Automation using Dockerfile

Advance Docker

Introduction to Docker-Compose

Exposure to Docker Swarm

Bonus Section

Working with Multiple Dockerfiles

Multiple Dockerfile use cases