What is Docker Compose? Multiple Containers & Docker Networking

Docker - Running Multiple Containers using Docker Compose & Docker Networking
#softwareengineering #docker #devops

In this video, we talk about how we can spawn multiple docker containers and make them interact with each other through basic docker networking. A docker compose file enables us to pack the configuration of multiple containers in one place and enables us to build multiple images, their network and containers.

▬▬▬▬▬▬ FULL DOCKER SERIES ▬▬▬▬▬▬
Basics to Production in less than 1 hour ↓

▬▬▬▬▬▬ CODE EXAMPLES & DOCUMENTATION ▬▬▬▬▬▬

▬▬▬▬▬▬ NEW TO DOCKER? ▬▬▬▬▬▬

▬▬▬▬▬▬ TIMESTAMPS ▬▬▬▬▬▬
00:00 Intro
00:47 Multi Service Applications
03:22 What is docker compose?
06:16 Running Multiple Containers
09:13 Docker Networking
12:29 Handling Dependencies
14:06 What's Next?

▬▬▬▬▬▬ SOCIALS ▬▬▬▬▬▬

▬▬▬▬▬▬ MY GEAR ▬▬▬▬▬▬

[MonisYousuf]

Links to code examples, docker basics and timestamps:



Timestamps:

00:00 Intro
00:47 Multi Service Applications
03:22 What is docker compose?
06:16 Running Multiple Containers
09:13 Docker Networking
12:29 Handling Dependencies
14:06 What's Next?

[MadhuKinneraDev]

Amazing video .. I spent 2 days with so many errors .. thank you

[bhuvaneshraj]

best docker compose video ever greatest explanation continue your work sir

[zdxzxzdxzx]

This video is covers more concepts and much better than some pluralsight courses! Great job.

[AdamtheADHDev]

This was incredibly clear and to the point. As an experienced dev trying to make use of docker, I got more insight from this one video than a bunch of others and reading some documentation combined!

[HamzahAhmad-dbcy]

Clear, and concise. The animations made the explanation ever clearer.
Thank you for the effort

[gazells]

Excellent explanation that cleared many doubts, can't wait for the next one!

[horvathmilcsi]

Very clear and focused presentation! Thank you!

[JuliBlu]

Awesome! I hope a lot of people support you by sharing your videos to their networks 🤞🏻 best of luck, Monis

[Afrolatina_adventurer]

I cant wait to see your next video! these are masterpieces

[martinsh]

I am not sure if this is your explanation style for all your videos; however, this one was one of the best explanation methods, at least for me.

[rolandschatzle]

Good video! All the concepts are well explained. 👍

[lolikpof]

i already knew all of that, but subscribed anyway cus the video is just so well done. Keep up the high quality!

[gavenblsn]

you are amazing. omg. unbelievable explanation.

[aimbrock]

Your content is really good. Much thanks.

[anbuarasanvellyan]

Great work 🎉 awesome,
May I know what tool you are using for these animations?

[VaibhavShewale]

ooh man need more of this also fast cause i have interview on this XD

[oleksiiprykhodko]

In the "yaml" file you can create a service and configure a name for its container with the container_name command. When we create a container with a given database and a container with a backend, what name should we give in the connection string (service name or container name)?

[hassanxelamin]

would love to know how this works for production vs local environments

[hyperoot]

Hey, Monis. I have a couple of questions. I hope you have some time to address those.

1. You "apps" seems completely developed where one can directly build it and deploy it (which you will explain in the next video). But generally, app development is never finished and we need to continuously make changes. Now, if there is only one developer, it's alright as we can simply make changes in the local and the `--build` flag will recreate the docker image. However, for a team working on the same project and/or if there are multiple branches of the code (prod, dev, test, etc.), can we leverage docker-compose to keep things streamlined?

2. vscode has a feature named dev-containers. This is great because I can create container and share that with anyone who want to develop with the tools and versions that I am using. They won't have to setup anything. They can run the container and have an exact replica of my dev environment. I am having hard time figuring out how to setup dev-containers for each segment of an app (frontend, backend, and DB for instance) that can communicate with each other while in the development phase.

3. At 7:44 you mentioned that we can provide environment variables into the docker-compose. I don't think it is secure at all as I can read the docker-compose file you have shared in the GitHub repo. How can I keep it safe? Is the only way to keep it secure is not to share the actual docker-compose file rather a censored version of it?

I am fascinated by DevOps and SecDevOps but I have very limited technical knowledge. If my queries doesn't make sense, let me know. I will try to clarify on what I mean by these questions.

Thanks for the all the efforts and videos. I look forward to the next one. I have one potential question regarding the content of the next video as well. Are we going to see IaaS where we deploy it within, let's say, AWS EC2 instance where we potentially have more control over the system or are we just planning to explore the SaaS version of this in AWS aka AWS ECS? Perhaps, you could show a contrast between these. (Just a suggestion) Basically, are we trying to outsource the job of the DevOps team to AWS or are we leveraging the features of cloud computing while retaining the control over the system and have our own DevOps team?

Cheers, HYP3R00T