Easy Docker for Developers

This is my first time leaving a review for Inflearn. (It may not be true.) I'm sorry to say this, but you are really amazing.. Docker is Docker, but you also teach me various theoretical bases, and thanks to you, I was able to re-confirm things that I was confused about or didn't remember well, so I'm having a great time with the lecture. But when I did the last practice in Section 5, a small error occurred when I launched the nginx container with a docker file. But what's the big deal about such a small thing in a lecture that contains such great meaning? I'll figure it out. Your voice is really nice, and I'm so grateful.... How did you distribute such an amazing lecture by clearly picking out only the necessary parts without explaining it in detail? I wonder if you made the lecture over 6 days and took a break on the 7th day? Or are you Docker itself? Is your MBTI Devops? I'll end my brief course review here, and I'll go listen to all the remaining lectures. I hope you stay healthy and become rich.

A lecture close to perfect, both in terms of learning and teaching method. If there were 5 stars, I'd give 5; if there were 100, I'd give 100. I watch many lectures due to my interest in teaching methods, but I often feel a sense of disappointment. I didn't feel that at all in this lecture. The advantages are as follows: 1. Terminology Explanation All terms are explained in an easy-to-understand manner. You might think, "Isn't that obvious?" but when listening to lectures on infrastructure or AWS, there are many terms used without explanation, like "You can provision the server." Especially in the IT industry, which is referred to as the curse of knowledge, terms are often used without explanation in lectures, but this lecture explains most terms in an easy-to-understand way. 2. Appropriate Time Lecture distribution with appropriate length, not boring. 3. Part Distribution Considerate of the Learner The part I like the most. The knowledge learned in Section 6 is applied in practice. Then theory appears again in Sections 7 and 8. In a typical lecture, the order of Sections 6 and 7, 8 would have been swapped, but here, when learners' focus starts to drop, or when what they've learned is about to be forgotten, practical parts are assigned to increase concentration. Also, even if you don't know the parts deferred until later, it doesn't significantly affect your ability to proceed with the practical part. If parts frequently used in the practical section were deferred, the practical section would become difficult. If all parts were explained before assigning the practical section, learners would get tired by the time they reach practice. This lecture proceeds with the Docker networking part deferred until after the practical section. While only planting anticipation for the Docker networking part during the practical part. In a typical lecture, the Docker networking would have been distributed before the practical section. This lecture distributes it later, using practice to rekindle interest when things get boring and having learners review what they've learned just through the lecture itself. Even if you're not interested in Docker, this is a must-watch lecture if you are interested in teaching methods.

I have taken quite a few lectures at Infraun, but this is the first time I have felt the need to write a review. This lecture is a great lecture for developers to understand Docker. Not only is it a good lecture for basic concepts and usage of Docker, but it also introduces prerequisite knowledge that you need to know to understand Docker technology. Personally, I especially liked the "Network Basics" lecture in the Docker Network section. Thank you for the great lecture.

I bought the lecture in the morning and started studying... After watching it, it was 2:30 in the morning... It was such a rich content that I couldn't help but watch it all the way through. It was such a rich day that I couldn't get my butt off except for meal times. I was impressed by the chapter progression that explained the concepts, organized the terms, and then proceeded with the practice. I wondered if he had learned a separate teaching method because it was easy to understand and the tips in between were very useful. In fact, I had some experience, so I knew Docker/Docker Compose/GitHub Actions, but I wish I had encountered it through this lecture when I first learned it. I was impressed. I felt a lot of preparation in the part where the structure of the commands was explained and the progress was made step by step with the code prepared in advance. It was a little expensive because it cost more than two books, but I felt like I had a proper tutoring session today ^^ Thank you. Youth room, run!! Here it is!!~~ - Ted -

When I learned the difference between VMware and Docker in the past, I didn't understand it well, and after that, I studied image build, Dockerfile, Docker Compose... and eventually gave up. This time, a new Docker lecture came out, and I watched various visual materials and short preview lectures on YouTube, and the delivery was very good, so I bought the lecture right away and listened to it every weekend. In conclusion, when explaining the theory, the visual materials were really easy for me to understand. I felt that explaining it with pictures rather than just words was especially important for understanding in the Docker lecture. After completing the lecture, I now have the ability to find the necessary commands by looking at the Docker documentation. And based on what I learned, I wrote the necessary parts of Docker Compose and Dockerfile myself and built a CI/CD GitHub Action pipeline for the first time and successfully deployed it. Maybe it's because I'm a college student, but there were still some parts of the Docker practical part that I didn't understand, but I think I've grown to the point where I don't feel averse to various terms such as image build, push, volume, network, etc. I am so lucky to have learned Docker through this course before getting a job. It was a really informative course that I didn't regret spending money on.

Thank you for the great lecture. It's been a long time since I've had a lecture with such meticulously prepared lecture materials. I haven't finished the lecture yet, but it's so fun and I'm learning about the things I knew vaguely one by one. If you explain Kubernetes or AWS in the next lecture, it would be informative and fun to watch. Thank you! + I think you have a Kubernetes lecture plan. I'd like to know the upload plan! (I'm going to take the class right away!)

This is a lecture that seems to be kindly taught by a close school senior. Rather than writing a single line of commands, this is a good lecture that defines why Docker appeared, how it is used, and how to use it well. If you are new to Docker, I strongly recommend starting with this lecture.

The explanation is so good that it's easy to understand. But the explanation is not too deep. It's a really good lecture to get started with Docker. Do you have any plans to make an easy Kubernetes lecture..? I'm studying infrastructure little by little, but Kuber is too difficult, so if the instructor makes one, I think I'll be able to learn it easily.