ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: 100+ Docker Concepts you Need to Know

Welcome to Docker 101.

If your goal is to ship software in the real world, one of the most powerful concepts to understand is containerization.

When developing locally, it solves the age-old problem of it works on my machine, and when deploying in the cloud, it solves the age-old problem of this architecture doesn't scale.

Over the next few minutes, we'll unlock the power inside this container by learning 101 different concepts and terms related to computer science, the cloud, and of course Docker.

I'm guessing you know what a computer is, right?

box that has three important components inside.

A CPU for calculating things, random access memory for the applications you're using right now, and a disk to store things you might use later.

This is bare metal hardware, but in order to use it, we need an operating system.

Most importantly, the OS provides a kernel that sits on top of the bare metal, allowing software applications to run on it.

In the olden days, you would go to the store and buy software to physically install it on your machine.

But nowadays, most software is delivered via the internet through the magic of networking.

When you watch a YouTube video, your computer is called the client, but you and billions of other users are getting that data from remote computers called servers.

When an app starts reaching millions of people, weird things begin to happen.

The CPU becomes exhausted handling all the incoming requests, disk IO slows down, network bandwidth gets maxed out, and the database becomes too large to query effectively.

On top of that, you wrote some garbage code that's causing race conditions, memory leaks, and unhandled errors that will eventually grind your server to a halt.

The big question is how do we scale our infrastructure?

A server can scale up in two ways, vertically or horizontally.

To scale vertically, you take your one server and increase its RAM and CPU.

This can take you pretty far, but eventually you hit a ceiling.

The other option is to scale horizontally, where you distribute your code to multiple smaller servers, which are often broken down into microservices that can run and scale independently.

But distributed systems like this aren't very practical when talking about bare metal, because actual resource allocation varies.

One way engineers address this is with virtual machines, using tools like Hypervisor.

It can isolate and run multiple operating systems on a single machine.

That helps, but a VM's allocation of CPU and memory is still fixed.

And that's where Docker comes in, the sponsor of today's video.

Applications running on top of the Docker engine all share the same host operating system kernel

and use resources dynamically based on their needs.

Under the hood, Docker's running a daemon or persistent process that makes all this magic possible and gives us OS-level virtualization.

What's awesome is that any developer can easily harness this power by simply installing Docker Desktop.

It allows you to develop software without having to make massive changes to your local system.

But here's how Docker works in three easy steps.

First, you start with a Docker file.

This is like a blueprint that tells Docker how to configure the environment that runs your application.

The Docker file is then used to build an image, which contains an OS, your dependencies, and your code, like a template for running your application.

And we can upload this image to the cloud to places like Docker Hub and share it with the world.

But an image by itself doesn't do anything.

You need to run it as a container, which itself is an isolated package running your code that in theory could scale infinitely in the cloud.

Containers are stateless, which means when they shut down, all the data inside them is lost.

But that makes them portable, and they can run on every major cloud platform without vendor lock-in.

Pretty cool, but the best way to learn Docker is to actually run a container.

Let's do that right now by creating a Docker file.

A Docker file contains a collection of instructions, which by convention are in all caps.

From is usually the first instruction you'll see, which points to a base image to get started.

This will often be a Linux distro, and may be followed by a colon, which is an optional image tag, and in this case specifies the version of the OS.

Next, we have the working directory instruction, which creates a source directory and CDs into it, and that's where we'll put our source code.

All commands from here on out will be executed from this working directory.

Next, we can use the run instruction to use a Linux package manager to install our dependencies.

Run lets you run any command just like you would from the command line.

Currently we're running as the root user, but for better security we could also create a non-root user with the user instruction.

Now we can use copy to copy the code on our local machine over to the image.

You're halfway there, let's take a brief intermission.

Now to run this code we have an API key, which we can set as an environment variable with the env instruction.

We're building a web server that people can connect to, which requires a port for external traffic.

Use the expose instruction to make that port accessible.

Finally, that brings us to the command instruction, which is the command you want to run when starting up a container.

In this case, it will run our web server.

There can only be one command per container, although you might also add an entry point, allowing you to pass arguments to the command when you run it.

That's everything we need for the Dockerfile.

But as an added touch, we could also use label to add some extra metadata, or we could run a health check to make sure it's running properly,

or if the container needs to store data that's going to be used later or be used by multiple containers, we could mount a volume to it with a persistent disk.

Okay, we have a Dockerfile, so now what?

When you install Docker Desktop, that also installed the Docker CLI, which you can run from the terminal.

Run Docker help to see all the possible commands, but the one we need right now is Docker build, which will turn this Docker file into an image.

When you run the command, it's a good idea to use the T flag to tag it with a recognizable name.

Notice how it builds the image in layers.

Every layer is identified by a SHA-256 hash, which means if you modify your Docker file, each layer will be cached, so it only has to rebuild what has actually changed,

and that makes your workflow as a developer far more efficient.

In addition, it's important to point out that sometimes you don't want certain files to end up in a Docker image, in which case you can add them to the Docker ignore file to exclude them from the actual files

that get copied there.

Now open Docker Desktop and view the image there.

Not only does it give us a detailed breakdown, but thanks to Docker Scout, we're able to proactively identify any security vulnerabilities for each layer of the image.

It works by extracting the software bill of material from the image and compares it to a bunch of security advisory databases.

When there's a match, it's given a severity rating, so you can prioritize your security efforts.

But now the time has finally come to run a container.

We can accomplish that by simply clicking on the run button.

Under the hood, it executes the docker run command, and we can now access our server on localhost.

In addition, we can see the running container here in docker desktop, which is the equivalent to the docker psst command,

which you can run from the terminal to get a breakdown of all the running and stop containers on your machine.

If we click on it though, we can inspect the logs from this container, or view the file system, and we can even execute commands directly inside the running container.

Now when it comes time to shut it down, we can use Docker stop to stop it gracefully, or Docker kill to forcefully stop it.

You can still see the shutdown container here in the UI, or use remove to get rid of it.

But now you might want to run your container in the cloud.

Docker push will upload your image to a remote registry, where it can then run on a cloud like AWS with Elastic Container Service,

or it can be launched on serverless platforms like Google Cloud Run.

Conversely, you may want to use someone else's Docker image, which can be downloaded from the cloud with Docker Pool.

And now you can run any developer's code without having to make any changes to your local environment or machine.

Congratulations, you're now a bona fide and certified Docker expert.

I hereby grant you permission to print out this certificate and bring it to your next job interview.

But Docker itself is only the beginning.

There's a good chance your application has more than one service, in which case you'll want to know about Docker Compose, a tool for managing multi-container applications.

It allows you to define multiple applications and their Docker images in a single YAML file, like a frontend, a backend, and a database.

The Docker Compose up command will spin up all the containers simultaneously, while the down command will stop them.

That works on an individual server, but once you reach massive scale, you'll likely need an orchestration tool like Kubernetes to run and manage containers all over the world.

It works like this.

You have a control plane that exposes an API that can manage the cluster.

Now, the cluster has multiple nodes or machines, each one containing a kubelet and multiple pods.

A pod is the minimum deployable unit in Kubernetes, which itself has one or more containers inside of it.

What makes Kubernetes so effective is that you can describe the desired state of the system, and it will automatically scale up or scale down,

while also providing fault tolerance to automatically heal if one of your servers goes down.

100

It gets pretty complicated, but the good news is that you probably don't need Kubernetes.

101

It was developed at Google based on its Borg system and is really only necessary for highly complex high-traffic systems.

102

If that sounds like you though, you can also use extensions on Docker Desktop to debug your pods.

103

And with that, we've looked at 100 concepts related to containerization.

104

Big shout out to Docker for making this video possible.

105

Thanks for watching, and I will see you in the next one.

📺 ช่องเดียวกัน

✨ วิดีโอแนะนำ

67 ประโยค

8 Most Important System Design Concepts You Should Know

Business EnglishUniversity StudentsWorking Adults

156 ประโยค

100+ Computer Science Concepts Explained

Business EnglishUniversity StudentsWorking Adults

187 ประโยค

How to ACTUALLY Get a DevOps Job in 2026

Business EnglishInterview EnglishUniversity Students

54 ประโยค

What is a server? Types of Servers? Virtual server vs Physical server 🖥️🌐

Business EnglishUniversity StudentsWorking Adults

102 ประโยค

What is Docker? Docker container concept explained || Docker Tutorial 1

Business EnglishUniversity StudentsWorking Adults

78 ประโยค

How I deploy serverless containers for free

Business EnglishUniversity StudentsWorking Adults

78 ประโยค

The easy way to keep your repos tidy.

Business EnglishUniversity StudentsWorking Adults

423 ประโยค

Free CCNA | VLANs (Part 2) | Day 17 | CCNA 200-301 Complete Course

Business EnglishUniversity StudentsWorking Adults

30 ประโยค

7 Phases of Penetration Testing Explained | Think your system is safe? #cybersecurity #pentesting

Business EnglishUniversity StudentsWorking Adults

13 ประโยค

Robots with connected brains

Business EnglishUniversity StudentsWorking Adults

74 ประโยค

LangChain in 5 Minutes (Explained Clearly)

Business EnglishUniversity StudentsWorking Adults

คำศัพท์และข้อสังเกตด้านการพูดสำหรับบทเรียนนี้

วิดีโอนี้มี 105 ประโยค และ 1837 คำ สำหรับฝึกพูดตาม ช่วงที่มีเสียงพูดยาว 8:27 ผู้พูดพูดเร็ว ประมาณ 217 คำต่อนาที จึงมีการเชื่อมเสียงและลดเสียงค่อนข้างมาก มีเพียง 79% ของคำที่อยู่ใน 3,000 คำที่ใช้บ่อยที่สุดในภาษาอังกฤษ คำศัพท์จึงค่อนข้างยาก

คำศัพท์สำคัญในวิดีโอนี้

คำที่ควรเรียนรู้ 15 คำจากวิดีโอ พร้อมคำอ่านและความหมาย:

คำศัพท์	คำอ่าน	ความหมาย
container คำนาม	/kənˈteɪ.nəɹ/	บรรจุภัณฑ์, หีบห่อ
server คำนาม	/ˈsɝvɚ/	เซิร์ฟเวอร์
cloud คำนาม	/ˈklaʊ̯d/	เมฆ
desktop คำนาม	/ˈdɛsktɒp/	พื้นโต๊ะ
layer คำนาม	/ˈleɪ̯ɚ/	ชั้น
database คำนาม	/ˈdeɪtəˌbeɪs/	ฐานข้อมูล
disk คำนาม	/dɪsk/	ดิสก์, จักร
execute คำกริยา	/ˈɛksɪˌkjuːt/	ประหาร
directory คำนาม	/dɪˈɹɛktəɹi/	ไดเรกทอรี
package คำนาม	/ˈpæk.ɪd͡ʒ/	หีบห่อ, ห่อ
solve คำกริยา	/sɒlv/	แก้, แก้ไข
terminal คำนาม	/ˈtɚmɪnəl/	อาคารผู้โดยสาร
upload คำกริยา	/ˈʌpˌloʊd/	อัปโหลด
expose คำกริยา	/ɪkˈspoʊz/	เผย, เปิดเผย
pod คำนาม	/ˈpɑd/	ฝัก

การออกเสียงที่ควรระวัง

ผู้พูดใช้รูปย่อและรูปลดเสียง 18 ครั้ง เช่น we're, you'll, you're ให้พูดแบบสั้นตามที่ได้ยิน

เสียง “sh” และ “zh”: instruction /ɪnˈstɹʌkʃən/, allocation /ˌæl.əˈkeɪ.ʃən/, extension /ɪkˈstɛnʃən/, efficient /ɪˈfɪʃənt/, congratulations /kənˌɡɹæt͡ʃəˈleɪʃ(ə)nz/
คำยาว — ลงเสียงหนักให้ถูกพยางค์: directory /dɪˈɹɛktəɹi/, developer /dɪˈvɛləpɚ/, allocation /ˌæl.əˈkeɪ.ʃən/, dependency /dɪˈpɛndənsi/, complicated /ˈkɑm.plɪˌkeɪ.tɪd/

วิธีฝึกกับวิดีโอนี้

ฟังวิดีโอให้จบหนึ่งรอบโดยยังไม่ต้องพูด แล้วจดคำที่ยังไม่รู้จัก
เริ่มที่ความเร็ว 0.75× พูดตามทีละประโยค แล้วกลับไปใช้ความเร็วปกติเมื่อเริ่มคล่อง
อัดเสียงตัวเองแล้วเทียบกับต้นฉบับ โดยสังเกตคำอย่าง container, server, cloud เป็นพิเศษ

ไวยากรณ์ในวิดีโอนี้

โครงสร้างที่ผู้พูดใช้บ่อยที่สุด พร้อมคำพูดจริงจากวิดีโอ:

โครงสร้าง	ในวิดีโอ
Passive voice be + กริยาช่อง 3 — เน้นสิ่งที่เกิดขึ้น ไม่ใช่ผู้กระทำ	is delivered · is called · are often broken
Relative clauses who / which + อนุประโยค — ข้อมูลเพิ่มเติมเกี่ยวกับคนหรือสิ่งของ	servers, which are · stateless, which means · colon, which is
Present perfect have/has + กริยาช่อง 3 — เหตุการณ์ในอดีตที่ยังเกี่ยวข้องกับปัจจุบัน	has actually changed · has finally come · we've looked

เทคนิค Shadowing คืออะไร?

Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ

เทคนิค shadowing: อ่านคู่มือฉบับเต็มทีละขั้นตอน →

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: 100+ Docker Concepts you Need to Know

10 very promising Open Source Projects you haven’t heard of

DNS Explained in 100 Seconds

Anthropic begged the world to stop AI… then shipped this

One man just liberated Fable... and now it’s illegal

7 Things No Programmer Ever Wants to Hear

80% of programmers are NOT happy… why?

Raspberry Pi Explained in 100 Seconds

Did Google just kickstart the intelligence explosion?

Tragic mistake... Anthropic leaks Claude’s source code

The one OpenAI announcement that can actually make you money...

When open-sourcing your code goes wrong...

Docker in 100 Seconds

The mystery is solved... and the answer is 40x cheaper than Claude

An ex-OpenAI researcher just deleted language from the LLM...

25 crazy software bugs explained

Git Explained in 100 Seconds

There's a new Linux distro in town for developers...

The "vibe coding" mind virus explained…

Linux got wrecked by backdoor attack

Nvidia CUDA in 100 Seconds

8 Most Important System Design Concepts You Should Know

100+ Computer Science Concepts Explained

How to ACTUALLY Get a DevOps Job in 2026

What is a server? Types of Servers? Virtual server vs Physical server 🖥️🌐

What is Docker? Docker container concept explained || Docker Tutorial 1

How I deploy serverless containers for free

The easy way to keep your repos tidy.

Free CCNA | VLANs (Part 2) | Day 17 | CCNA 200-301 Complete Course

7 Phases of Penetration Testing Explained | Think your system is safe? #cybersecurity #pentesting

Robots with connected brains

LangChain in 5 Minutes (Explained Clearly)

คำศัพท์และข้อสังเกตด้านการพูดสำหรับบทเรียนนี้

คำศัพท์สำคัญในวิดีโอนี้

การออกเสียงที่ควรระวัง

วิธีฝึกกับวิดีโอนี้

ไวยากรณ์ในวิดีโอนี้

เทคนิค Shadowing คืออะไร?