Shadowing Practice: 100+ Docker Concepts you Need to Know - Learn English Speaking with Video
בחר מצב תרגול
כל מצב פותח חדר תרגול במסך מלא.
105 משפטים
אם המשפטים קצרים או ארוכים מדי, לחץ על ערוך כדי להתאים אותם.
1
Welcome to Docker 101.
2
If your goal is to ship software in the real world, one of the most powerful concepts to understand is containerization.
3
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.
4
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.
5
I'm guessing you know what a computer is, right?
6
box that has three important components inside.
7
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.
8
This is bare metal hardware, but in order to use it, we need an operating system.
9
Most importantly, the OS provides a kernel that sits on top of the bare metal, allowing software applications to run on it.
10
In the olden days, you would go to the store and buy software to physically install it on your machine.
11
But nowadays, most software is delivered via the internet through the magic of networking.
12
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.
13
When an app starts reaching millions of people, weird things begin to happen.
14
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.
15
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.
16
The big question is how do we scale our infrastructure?
17
A server can scale up in two ways, vertically or horizontally.
18
To scale vertically, you take your one server and increase its RAM and CPU.
19
This can take you pretty far, but eventually you hit a ceiling.
20
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.
21
But distributed systems like this aren't very practical when talking about bare metal, because actual resource allocation varies.
22
One way engineers address this is with virtual machines, using tools like Hypervisor.
23
It can isolate and run multiple operating systems on a single machine.
24
That helps, but a VM's allocation of CPU and memory is still fixed.
25
And that's where Docker comes in, the sponsor of today's video.
26
Applications running on top of the Docker engine all share the same host operating system kernel
27
and use resources dynamically based on their needs.
28
Under the hood, Docker's running a daemon or persistent process that makes all this magic possible and gives us OS-level virtualization.
29
What's awesome is that any developer can easily harness this power by simply installing Docker Desktop.
30
It allows you to develop software without having to make massive changes to your local system.
31
But here's how Docker works in three easy steps.
32
First, you start with a Docker file.
33
This is like a blueprint that tells Docker how to configure the environment that runs your application.
34
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.
35
And we can upload this image to the cloud to places like Docker Hub and share it with the world.
36
But an image by itself doesn't do anything.
37
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.
38
Containers are stateless, which means when they shut down, all the data inside them is lost.
39
But that makes them portable, and they can run on every major cloud platform without vendor lock-in.
40
Pretty cool, but the best way to learn Docker is to actually run a container.
41
Let's do that right now by creating a Docker file.
42
A Docker file contains a collection of instructions, which by convention are in all caps.
43
From is usually the first instruction you'll see, which points to a base image to get started.
44
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.
45
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.
46
All commands from here on out will be executed from this working directory.
47
Next, we can use the run instruction to use a Linux package manager to install our dependencies.
48
Run lets you run any command just like you would from the command line.
49
Currently we're running as the root user, but for better security we could also create a non-root user with the user instruction.
50
Now we can use copy to copy the code on our local machine over to the image.
51
You're halfway there, let's take a brief intermission.
52
Now to run this code we have an API key, which we can set as an environment variable with the env instruction.
53
We're building a web server that people can connect to, which requires a port for external traffic.
54
Use the expose instruction to make that port accessible.
55
Finally, that brings us to the command instruction, which is the command you want to run when starting up a container.
56
In this case, it will run our web server.
57
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.
58
That's everything we need for the Dockerfile.
59
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,
60
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.
61
Okay, we have a Dockerfile, so now what?
62
When you install Docker Desktop, that also installed the Docker CLI, which you can run from the terminal.
63
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.
64
When you run the command, it's a good idea to use the T flag to tag it with a recognizable name.
65
Notice how it builds the image in layers.
66
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,
67
and that makes your workflow as a developer far more efficient.
68
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
69
that get copied there.
70
Now open Docker Desktop and view the image there.
71
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.
72
It works by extracting the software bill of material from the image and compares it to a bunch of security advisory databases.
73
When there's a match, it's given a severity rating, so you can prioritize your security efforts.
74
But now the time has finally come to run a container.
75
We can accomplish that by simply clicking on the run button.
76
Under the hood, it executes the docker run command, and we can now access our server on localhost.
77
In addition, we can see the running container here in docker desktop, which is the equivalent to the docker psst command,
78
which you can run from the terminal to get a breakdown of all the running and stop containers on your machine.
79
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.
80
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.
81
You can still see the shutdown container here in the UI, or use remove to get rid of it.
82
But now you might want to run your container in the cloud.
83
Docker push will upload your image to a remote registry, where it can then run on a cloud like AWS with Elastic Container Service,
84
or it can be launched on serverless platforms like Google Cloud Run.
85
Conversely, you may want to use someone else's Docker image, which can be downloaded from the cloud with Docker Pool.
86
And now you can run any developer's code without having to make any changes to your local environment or machine.
87
Congratulations, you're now a bona fide and certified Docker expert.
88
I hereby grant you permission to print out this certificate and bring it to your next job interview.
89
But Docker itself is only the beginning.
90
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.
91
It allows you to define multiple applications and their Docker images in a single YAML file, like a frontend, a backend, and a database.
92
The Docker Compose up command will spin up all the containers simultaneously, while the down command will stop them.
93
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.
94
It works like this.
95
You have a control plane that exposes an API that can manage the cluster.
96
Now, the cluster has multiple nodes or machines, each one containing a kubelet and multiple pods.
97
A pod is the minimum deployable unit in Kubernetes, which itself has one or more containers inside of it.
98
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,
99
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.
הורד אפליקציה
כל מה שאתה צריך כדי לדבר בשטף
הגיית AIציון לכל משפט
תרגול IPAשלוט בכל צליל
אוצר מיליםבנה את מאגר המילים שלך
משחק אוצר מיליםלמד תוך כדי משחק
אותו ערוץ
C11
PostgreSQL in 100 Seconds
Daily ConversationWorking Adults
C11
React Native in 100 Seconds
Daily ConversationUniversity Students
C13
Every app on Earth is now open source... whether it likes it or not
Daily ConversationWorking Adults
C14
Brainf**k in 100 Seconds
Daily ConversationUniversity Students
C13
OpenAI’s lead engineer was secretly a spy...
Daily ConversationUniversity StudentsWorking Adults
C12
Mind-bending new programming language for GPUs just dropped...
Daily ConversationUniversity Students
C12
China just dropped a new frontier model... and nobody can explain how
Daily ConversationUniversity StudentsWorking Adults
C19
The most interesting "hack" in history...
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
The last real programmers are dying out...
Daily ConversationUniversity StudentsWorking Adults
C11
Did the AI bubble just pop?
Daily ConversationUniversity StudentsWorking Adults
C130
Docker in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C16
The plan to break apart Google... RIP Chrome
American AccentBusiness EnglishDaily ConversationUniversity Students
C210
Angular in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
B23
OpenAI’s new browser feels familiar…
American AccentBusiness EnglishUniversity StudentsWorking Adults
C15
Tragic mistake... Anthropic leaks Claude’s source code
American AccentBusiness EnglishUniversity StudentsWorking Adults
B23
Firefox and Tor hit with 9.8 critical level exploit
American AccentBusiness EnglishUniversity StudentsWorking Adults
B23
5 open source tools that replaced my $320/mo AI stack...
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
C++ in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
B24
Linux in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C13
Did Google just dethrone OpenAI and Anthropic?
Daily ConversationUniversity StudentsWorking Adults
FOR YOU
המלץ על סרטון
C18
67 משפטים
8 Most Important System Design Concepts You Should Know
Daily ConversationUniversity StudentsWorking Adults
C11
176 משפטים
Every Networking Concept Explained | Networking 101 (2026)
Daily ConversationUniversity StudentsWorking Adults
C13
173 משפטים
STOP Running Code On Your Computer
Daily ConversationUniversity StudentsWorking Adults
C15
59 משפטים
There's a new Linux distro in town for developers...
American AccentDaily ConversationUniversity StudentsWorking Adults
C11
433 משפטים
Give Me 24 minutes, I'll Give You 1,000+ hours of Claude Knowledge
Daily ConversationUniversity StudentsWorking Adults
C12
102 משפטים
What is Docker? Docker container concept explained || Docker Tutorial 1
Daily ConversationUniversity StudentsWorking Adults
C11
78 משפטים
How I deploy serverless containers for free
Daily ConversationUniversity StudentsWorking Adults
C164 משפטים
Iran’s $60B Oil Machine: How Millions of Barrels Reach the USA
Daily ConversationUniversity StudentsWorking Adults
C11
364 משפטים
Running AI Agents in Secure Sandboxes with E2B & Docker MCP | Docker’s AI Guide to the Galaxy
Daily ConversationUniversity StudentsWorking Adults
C11
68 משפטים
GitHub Copilot now controls your command line...
Daily ConversationUniversity StudentsWorking Adults
C11
40 משפטים
The Engineering that Runs the Digital World 🛠️⚙️💻 How do CPUs Work?
Daily ConversationUniversity StudentsWorking Adults
אוצר מילים והערות הגייה לשיעור הזה
שיעור הדיבור הזה ברמה C1 מבוסס על הסרטון “100+ Docker Concepts you Need to Know”. המילים שחוזרות הכי הרבה: docker, container, image, command, file. בסרטון הזה יש 105 משפטים ו-1837 מילים לתרגול Shadowing. הדיבור נמשך 8:27. הדובר מדבר מהר, כ-217 מילים בדקה, אז צפו לצלילים מחוברים ומקוצרים. רק 79% מהמילים נמצאות בין 3,000 המילים הנפוצות ביותר באנגלית, כך שאוצר המילים מאתגר.
אוצר מילים מרכזי בסרטון הזה
15 המילים המתקדמות ביותר בסרטון, עם ההגייה והמשמעות שלהן:
| מילה | הגייה | משמעות |
|---|---|---|
| container שם עצם | /kənˈteɪ.nəɹ/ | מיכל |
| execute פועל | /ˈɛksɪˌkjuːt/ | להוציא להרוג |
| disk שם עצם | /dɪsk/ | דִּיסְק |
| distribute פועל | /dɪˈstɹɪbjuːt/ | חילק |
| persistent שם תואר | /pəˈsɪstənt/ | עקשן |
| certify פועל | /ˈsɜː.tɪ.faɪ/ | וידא |
| colon שם עצם | /ˈkoʊ.lən/ | נקודתיים |
| bandwidth שם עצם | /ˈbændwɪdθ/ | רוחב פס |
| hash שם עצם | /ˈhæʃ/ | סוּלָּמִית |
| cache שם עצם | /kæʃ/ | מִצְבּוֹר, מַחְבּוֹא |
| harness פועל | /ˈhɑɹ.nəs/ | רָתַם |
| template שם עצם | /ˈtɛm.plɪt/ | תַּבְנִית, שַׁבְּלוֹנָה |
| exclude פועל | /ɪksˈkluːd/ | לא הכליל |
| calculate פועל | /ˈkælkjʊleɪt/ | חישב \ חִשֵּׁב |
| unlock פועל | /ʌnˈlɑk/ | פתח |
Phrasal verbs שתשמעו
| מילה | משמעות |
|---|---|
| go down פועל | ירד |
משפטים שכדאי לחזור עליהם
משפטים קצרים ושלמים מהסרטון שאפשר להשתמש בהם בשיחה יומיומית:
- I'm guessing you know what a computer is, right?
- The big question is how do we scale our infrastructure?
- You're halfway there, let's take a brief intermission.
דקדוק בסרטון הזה
המבנים שהדובר משתמש בהם הכי הרבה, עם המילים המדויקות מהסרטון:
| מבנה | בסרטון |
|---|---|
| סביל (Passive voice) be + past participle — הדגש הוא על מה שקורה, לא על מי שעושה את הפעולה | is delivered · is called · are often broken |
| משפטי זיקה (Relative clauses) who / which + clause — מידע נוסף על אדם או דבר | servers, which are · stateless, which means · colon, which is |
| הווה מושלם (Present perfect) have/has + past participle — פעולה שקרתה בעבר ועדיין יש לה חשיבות או השפעה עכשיו | has actually changed · has finally come · we've looked |
הגייה ששווה לשים לב אליה
הדובר משתמש ב-18 קיצורים וצורות מקוצרות, כמו we're, you'll, you're. אמרו אותם בצורה הקצרה, כפי שאתם שומעים אותם.
- הצלילים של “sh” ו-“zh”: allocation /ˌæl.əˈkeɪ.ʃən/, intermission /ɪntɚˈmɪʃən/, hash /ˈhæʃ/, cache /kæʃ/, optional /ˈɑp.ʃə.nəl/
- מילים ארוכות — שימו לב להטעמה: directory /dɪˈɹɛktəɹi/, vertically /ˈvɝ.tɪ.kəli/, dependency /dɪˈpɛndənsi/, allocation /ˌæl.əˈkeɪ.ʃən/, intermission /ɪntɚˈmɪʃən/
צלילים שדוברי עברית מתקשים בהם:
- /w/ — שפתיים מעוגלות, לא /v/: workflow /ˈwɝkfloʊ/, bandwidth /ˈbændwɪdθ/, query /ˈkwɪɹ.i/, halfway /ˌhæfˈweɪ/
- /æ/ — פתוח יותר מה-“אֶ” העברית, לא כמו “a” ב-“cup”: allocation /ˌæl.əˈkeɪ.ʃən/, proactively /pɹoʊˈæk.tɪv.li/, bandwidth /ˈbændwɪdθ/, hash /ˈhæʃ/, cache /kæʃ/
- /r/ — הלשון לא נוגעת בשום מקום, לא ה-“ר” הגרונית: container /kənˈteɪ.nəɹ/, directory /dɪˈɹɛktəɹi/, distribute /dɪˈstɹɪbjuːt/, blueprint /ˈbluːˌpɹɪnt/, configure /kənˈfɪɡə(ɹ)/
איך לתרגל עם הסרטון הזה
- הקשיבו לכל הסרטון פעם אחת בלי לדבר, ורשמו את המילים שאתם לא מכירים.
- התחילו במהירות 0.75×, תרגלו Shadowing משפט אחר משפט, וחזרו למהירות רגילה כשזה מרגיש קל.
- הקליטו את עצמכם והשוו למקור, תוך תשומת לב למילים כמו container, execute, disk.
מהי טכניקת השאדואינג?
שאדואינג היא טכניקת למידת שפה מבוססת מדע שפותחה במקור להכשרת מתורגמנים מקצועיים ופופולרית על ידי הפוליגלוט ד"ר אלכסנדר ארגואלס. השיטה פשוטה אך עוצמתית: אתה מקשיב לאודיו באנגלית ילידית וחוזר עליו בקול רם מיד — כמו צל העוקב אחרי הדובר עם עיכוב של 1–2 שניות בלבד. בניגוד להאזנה פסיבית או תרגילי דקדוק, שאדואינג מכריח את המוח והשרירים בפה לעבד ולשחזר דפוסי דיבור אמיתיים בו זמנית. מחקרים מראים שזה משפר משמעותית את דיוק ההגייה, האינטונציה, הקצב, הדיבור המחובר, הבנת השמיעה ושטף הדיבור — מה שהופך אותו לאחת השיטות היעילות ביותר להכנה לIELTS Speaking ולתקשורת באנגלית בעולם האמיתי.