Thank you for your comments and many messages about the leaked password. What a community 💙 Already updated it 👍 If this video was helpful, be sure to subscribe and give a like 😊 Also any tips or learnings you want to share with others? 👀
Hated alternative video from NetworkChuck, fully of fancy animation, fluff and camera focused on the presenter and he starts writing the compose file immediately! Here, you get to know what problem are you trying to solve first, then how to do it. The logic flows seamlessly in a well-thought-out manner.
Thank you for such a great demo of Warp's features in your video, Nana! Outside of the sponsorship, you did an amazing job with this video. We loved the comparison of what life would be like without Docker Compose & your comparison of Docker Compose vs Kubernetes at the end. Viewers, if you do end up trying out Warp, please let us know if you run into any issues or have feedback 👍
Thank you again Nana, You are officially my primary mentor in devops. Your content is so direct and you pack so much in the limited time without us feeling overwhelmed. Keep doing the great work.
This tutorial is perfect for people who want to start with docker-compose. I use it for a couple of years already. I was a little surprised you used 'docker build' and 'docker push' to build and push the image to the registry. I use docker-compose for that as well. Just supply the image and build arguments in the yaml file and it works with just 'docker-compose build' and 'docker-compose push' as well. This also makes it less complicated.
I'm only 16 minutes into your tutorial, but I want to pause to let you know that I really appreciate your clear communication. It's so refreshing. Thank you. I'll check back later.
Thank you very much for your videos. They are very helpful and motivate me to study. May God give you strength and health to continue sharing my experience and knowledge.
@TechWorldwithNana web-application part: I think it is better to use `npm ci` instead of `npm install` to ensure consistency and speed; especially in production. :) (I understand that this is just an example, but I think, it may be worth showing production-oriented orders.) ```Dockerfile FROM node:20-alpine # Set the working directory in the container (If the directory does not exist, Docker will create it.) WORKDIR /home/app # Copy the application files to the working directory in the container COPY ./app . # Install dependencies using npm ci for consistency and speed RUN npm ci # no need for /home/app/server.js [...] ``` Thanks again for your superb content!
Everything about the containerized environment, Docker, Kubernetes, Prometheus, minikube, Terraform, Ansible and a lot more I learned only from your videos that successfully landed me a great job as a Senior Software Engineer, There is nothing on your channel that I didn't look. Thank you so much for giving the right path.
version in yaml start is optional. From docs: The top-level version property is defined by the Compose Specification for backward compatibility. It is only informative. Compose doesn't use version to select an exact schema to validate the Compose file, but prefers the most recent schema when it's implemented.
Such a well-explained video. I think 1Hr max is a good time to not lose your focus and understand topics easily. Thanks for the video and the high quality of it. Keep it up!
amazing video. I did the example in a computer running Win10, VSC, and Git bash. Running from the terminal in Visual Studio Code I had to create environment variable with this command: # ======================================================== # Note: # To create enviroment variables in Linux and Mac run this: # export MY_VARIABLE="my_value" # echo $MY_VARIABLE # To create environment variables in Powershell VSC terminal # $env:MY_VARIABLE="my_value" # echo $env:MY_VARIABLE # ======================================================== Thanks Nana, your videos are super usefull.
First, thank you very much for sharing all your knowledge, I have learnt A LOT today. Second, looks like docker componse has been migrated from python (v 1.0) to GO (v 2.0) so now is part of the docker command itself, without the "-". Just in case someone is trying to install something "new" while watching this video (like me :D).
Nana, After watching the Docker crash course video, you became my idol. Could you release a new Kubernetes crash course video in 2024? I really want to learn Kubernetes at this time.
Thank you for this video Nana. My only suggestion is to format the video such that the RU-vid miniplayer control/progress bar would not overlap with the CLI commands that you are typing.
Thank you for this video. I do have a few comments/suggestions: - had to add - container_name: mongo in the mongedb service for it to work, don't know why. - ports: - 27017:27017 exposes mongo to the host, but is not necessary in this example because in the stack the containers can access each others ports anyway. Expose as little as necessary. - There's the .env file for setting the env vars which is read by default if present - now there is "docker compose" which is written in Go as opposed to "docker-compose" (python version if I'm correct)
Thank you so much for great video and valuable information, we are waiting for some videos related Docker file, Docker stack, and finally waiting for Azure devops course which will be golden gifted
docker ✅ docker compose ✅ onto kubernetes 👍🏻 thank you so much for these crash course series and packing just the right amount of information to get a birds eye view of how these systems work.
Nana thanks for everything and i love how you teaching. I would like to suggest to you, since you use Warp, to configure it to display the terminal input lines at the top. I say this because, in my case, as I watch with subtitles sometimes, the lines get mixed up
Docker secrets only work with docker swarm and docker stacks. So the compose file has to be “adapted” to v3 docker swarm. And that is a problem when u have a complex docker compose file :( Btw, if I am using mozila sops service inside the compose file: how can I assign the value of the decrypted credentials, so the next Service can use those credentials? Pls
I was following your Docker Tutorial for Beginners [FULL COURSE in 3 Hours] and I got some questions:- 1. I'm running this NodeJs app on an AWS EC2 instance. How do I get the Public IP address of my instance in the index.html and server.js file automatically cuz every time I start the instance the IP address gets changed. 2. How do I get the Public IP in the container.
