Docker Compose Tutorial
Вставка
- Опубліковано 21 бер 2022
- Learn all about Docker Compose so you can orchestrate your services with confidence!
- Get the complete Docker course (zero to hero): bit.ly/3sO7Z5H
- Subscribe for more Docker tutorials like this: goo.gl/6PYaGF
⭐️ Want to learn more from me? Check out these links:
Courses: codewithmosh.com
Twitter: / moshhamedani
Facebook: / programmingwithmosh
Blog: programmingwithmosh.com
#Docker #DevOps
Docker is the de facto standard for building, shipping and running applications in a consistent manner. That's why most companies use it and are looking for developers with Docker skills. If you're looking for a career in software or DevOps engineering, you must have Docker on your resume. And not only that, you should know it well and be able to use it to effectively package and deploy your applications.
thank you!! where is the zip file you mantion in 5:54?
Just starting my coding journey and found your website and courses by accident. Couldn't be more thankful for what you have put together. You're such a gifted teacher! Learning SO much thanks to you!! :)
did you get the zip file?
@@edwinchiboko3737 yah dude where is the zip file
I have learned everything from watching your video. You are my teacher
I watch your video at least once a day. A lot of people are learning because of you
Thank you very much 🙏
You're the frickin' BEST teacher here, Mosh! Man, if I become a IT teacher one day, I hope I can be like you! You explain everything so clearly, you seem to understand what people need to get something. That comparision you did beetween json and yaml what GOD TIER.
I bought you Redux course and IT WORTH EVERY CENT!
How can you find the code?
did you get the zip file
I really enjoy and appreciate all your work, you make the world better with your courses where you combine all necessary knowledge and tools for programming. I really love programming and, for sure, you made me love it! Peace and Love from Ukraine!❤️
Did you find the zip file?!!
thank you Mosh for your high quality and amazing tutorials. wish you the best.
Finally the legend is back 😎
Thank you! Please support me by liking and sharing this video. :)
Learning is a continuous process
Absolutely mosh!..
Done :-)
@@programmingwithmosh Hello Sir! How can I Unsubscribe Code with Mosh? I've Completed My courses. Thanks a Lot!
0:00 Intro
0:27 Running Multi-container Apps (intro)
1:16 Installing Docker Compose
2:30 Cleaning Up our Workspace (delete containers and images)
5:39 The Sample Web Application
8:50 JSON and YAML Formats
13:00 Creating a Compose File
21:58 Building Images
25:38 Starting and Stopping the Application
27:49 Docker Networking
Where is that bloody zip file?
how can I get the ZIP file?
where is zip? can you please link?
Superb Mosh-jan. Thank you. I say this without prejudice. Content is fluid, it stops to point out significant landmarks without cluttering, and therefore the duration is also tolerable in this age of millisecond attention spans. I learned a lot and refreshed a lot.
did you get the zip file
I only appreciate your lectures after going through the ones done by others. This guy is a genius teacher.
did you get the zip file
I couldn't be more thankful for what you do!
You are AMAMAMAMAZING Mosh.. God Bless you for the free stuff!
This video cleared my doubts, love the content.
You're a life saver Mosh, this is just what I was looking for💯
did you get the zip file
I like your tuts very much dude. Simple but practical
If you are wondering why the version number is string, it's because version can be something like 3.8.1 which is not a number.
You are the best teacher ever you explain once and I allredy understand.😄😄
at 5:50 you mentioned the zip, there is not zip file link in the video description.
Regarding JSON vs YAML: It's not only about performance, but also about validation and security.
If you, e.g. copy+move some lines from a JSON file to another location, most likely, the JSON will be corrupt and incorrect, and if not, it's very likely, the order didn't matter anywhere. That's good behaviour for anything that mainly computers operate, as such a copy+paste error easily happens while editing (or merging with git), but might not be reviewed by (many) humans, so might be undetected for a long time. In YAML, there is a good chance, randomly moving blocks around, the end result is a different, but still correct YAML. Indeed, that's such a common error, that for bigger projects you usually have to write an own linter for the yaml files checking e.g. if the keys are the expected ones. Regarding security: YAML specification is a bit bigger than XML, so it contains a lot of hard to implement and possible insecure options. That's why many first naive implementation of YAML parsers in programming languages were replaced over time by other parser only implementing a secure subset of YAML. (Or alternatively that's tackled by the custom linters you have to write anyway)
There are some other subtle problems with YAML, e.g. your question of why you have to put "3.8" in quotes is because otherwise it would be detected as float und depending of whether can be represented in binary internally exactly or only close to it (indeed, 3.8f == 3.7999999523162841796875). The easiest way to enforce consistency is to demand that the version is always a string and not sometimes a string (3.8.0 == "3.8.0"), sometimes a float (3.8 == 3.7999999523162841796875) and sometimes an int (4 == 4).
There are many more subtle possibilities to misinterpret the unquoted strings: Magic words like true or false are becoming booleans. A minus sign is very often interpreted as list start, several further characters like +, |, also have special meanings and so on. When in doubt, always put your strings into quotes, from a practical standpoint that the system should what we want to say in the yaml, even though readability is reduced.
That's why, where high predictability is wanted, often enough different formats are used with less surprisings. E.g. HCL for Terraform, Programming languages for Pulumi, AWS CDK, ... or just toml/ini files.
Anyway, the high readability, easy understanding and universal structure of YAML dominates pretty much every modern stack, so the solution to all the above problems are custom linters and performant YAML parsers (most often with an own subset or dialect).
BTW, JSONs have disappointing also ambiguities that can even be exploited, e.g. the spec does not tell anything what should happen if a key is duplicated (which value to take). Different parsers handle that differently, and for the right combination, you can pass the validation done by the first parser to then inject some malicious (or just unintended, unwanted) behaviour to the second parser.
Thanks for the info man
Really appreciate your content Mosh!
Thank you Mosh, you always make good tutorial!
Thank You Mosh! I'm gonna take your course!
It would be great if you could make a course on Devops tools ( Open source tools ) with the CI /CD Pipeline.
Thank You Mosh. This tutorial was great!
Thank you so much for this wonderful tutorial
so proud of You Mosh ! I'm from Iran , Hamedan too. !!
Congrats ! The course is awsome ! Thank you :)
Mosh we are so glad to see you're back
thanks Mosh. as always, great tutorial.
Really great videos , well explained , just awesome !
I learned so much from your 6 hours python course .Thank you so much Mosh🙏
Happy to see you brother!! Love from India 😍
thank you so much for shaing your knowledge in an intersting way
Hello Mosh! Thank you for making these amazing tutorials. Could you please link the zip file that you are referring to in this video so that we can follow along? Thank you!
This was really helpful. Thank you.
I really enjoy ur videos with great understanding, I want to be a software developer but I don't know which programming language to learn first, and where to start 😶
This was one hell of a great video. You have a great teaching style. You are VERY clear in your explanations. And best of all, your screen captures are MOBILE-FRIENDLY. This video was missing the 1 thing I came looking for, but I am glad I watched the whole thing. Liked. Subscribed. Will look over your courses and purchase any that are remotely relevant to my needs. ☮❤🌈
PS: What I needed was how to do a "reverse port map/access". That is, I need initiate "from contain to host", instead of the "from host to container" that is explained EVERYWHERE. I have since learned this is done via `docker run --add-host=host.docker.internal:host-gateway` or in docker-compose.yaml `extra_hosts: ["host.docker.internal:host-gateway"]` Then [for example] your container can access the CUPS printer on your host machine via port: 631 on host: host.docker.internal
Great explained. Thank you so much.
good stuff. thank you. now the world needs your take on svelte!
Thank you for this tutorial, I was having problems until I saw your video thank you very much
what a great content! so grateful to you
Really really it's great to see u on live ❤️❤️
Where is the Zip file? As stated in this video at 5:47...
Being a metalhead for decades. I just found my new favorite person and that guy's name is Mosh! \M/
Great tutorial , that helped me well
Thanks
my king mosh i love you so so much, you taught me how to be the best programmer big love from africa Ethiopia.
Thank you! Please support me by liking and sharing this video. :)
@@programmingwithmosh Where is the Zip file? 5:56 ????
just wondering where the zip file is located??
yeah... same here!
You're an excellent tutor.
You're a Pro, Mosh! Thanks vm
Thanks, very useful. Well done.
I hope you will continue and thank you very much
you are my teacher
I love your tutorials
Great video, Thank you!
Thank you for the explanation
Amazing tutorial
Thanks for your excellent video!! Where I can download the files did you use in your examples?
super helpful, thanks!
Thanks for this tutorial!!!
You're the best mosh ❤️💙
Your are the best "mosh".. no one can beat you
Thank you! Please support me by liking and sharing this video. :)
Flutter tutorial please, we have all been waiting so long for that 😀👍
Amazing tutorial! i'm so tired of just stackOverflow codes without explain, thanks so much!
thank you mosh ...lovely !!
I just want to let you know that your courses are top class.
One improvement I would like to see in your course is the project you develop during the lectures. Even though *Vidly* is really a good project, I would like to see much complex project than that. Maybe an e-commerce project. Point is: you have tons of cool techniques to improve the quality of code which we can learn from your experience.
Where can I find the Vidly zip file ?
Thanks for sharing, it was a useful video.
Very Very Thank Your videos are very good.
Hi, what are your terminal configurations for the highlighted autocomplete? Thanks.
This guy is thug, everything is easy in his world. Thanks so much for all the effort Moch!
The reason version has to be in quotes for docker-compose is that yaml spec parses numbers such as 3.0 to 3 and it breaks versioning.
Nice tutorial, thanks. It's full of valuable information.
👆send a direct message for support and guidance
at 5:50 you say that below the video is a zip file, but there is no zip file.
I looked for the zip file as well but couldn't find
Fantastic course
Need more videos on docker Thanks!
Which theme did you use in vs code for HTML and CSS tutorial?
what is the difference between docker-compose and docker compose.. I noticed that I'm getting an error when I use docker-compose but everything works well when I change it to docker compose .. without the dash
What vs code extensions and terminal do you use?
Great Video. I am new to docker compose. I tried the same steps as per your docker compose file but gut this error. nable to prepare context: path "./frontend" not found does VS Code follow indentation?
Hi mosh I was seeing that the code on python was not with the @client.event part and I’m very confused could you help me on what to do
Great job 👍.
Thanks for this wonderful tutorial.
I'm trying to follow however could not find the link to download the zip file.
Is there really a zip file attached below the video? I can't find it. Anyone? Thanks!
Helpful , thanks
Where's the ZIP file you were talking about attached belowed - i'm unable to find it
nicely explained
14:09 I think that could be to allow subversions like 3.8.2 etc which would not translate well as numbers.
Also, version is deprecated and ignored by docker. It's literally just a comment at this point. From Docker spec (emphasis in original): "A Compose implementation SHOULD NOT use this version to select an exact schema to validate the Compose file, but prefer the most recent schema at the time it has been designed."
5:51
where is the zip file ?
You are awesome 🔥🔥
You are always awesome. Everybody loves you :)
hi moshi, long time , you the best man
Very good tutorial
Thanks for sharing
Hi Mosh,
what IDE are you using and is it on Mac or Windows? Thanks
Are you sharing the code for this tutorial anywhere?
Great work and thanks again! I like that VS Code editor color scheme. What is that called?
I was waiting for this ep. and enjoyed it!!!!! :DDDDD
But can you please make a c++ beginner tutorial?
Where can I find the zip file for backend and frontend projects mentioned in the video?
Same question here =(
I don't know either so replying here so hopefully I get a notification if someone tells you.
Purchase the course
Love it, I’m being stuck for 2 weeks
what a great video !!!
How can one determine what the needs of the project are for a docker compose file? How do you know what the requirements are?
Awesome thanks