Shadowing Practice: 100+ Docker Concepts you Need to Know - Learn English Speaking with Video
Les maken...
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.
📺 Zelfde Kanaal
C11
PostgreSQL in 100 Seconds
C12
DNS Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
B23
Anthropic begged the world to stop AI… then shipped this
American AccentBusiness EnglishUniversity StudentsWorking Adults
B23
A $6.3 billion open-weight model just got embarrassed by the French...
B22
7 Things No Programmer Ever Wants to Hear
American AccentBusiness EnglishWorking Adults
B21
80% of programmers are NOT happy… why?
American AccentBusiness EnglishUniversity StudentsWorking Adults
B24
Raspberry Pi Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C13
Tragic mistake... Anthropic leaks Claude’s source code
American AccentBusiness EnglishUniversity StudentsWorking Adults
C129
Docker in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C13
The mystery is solved... and the answer is 40x cheaper than Claude
American AccentBusiness EnglishUniversity StudentsWorking Adults
B28
An ex-OpenAI researcher just deleted language from the LLM...
American AccentBusiness EnglishUniversity StudentsWorking Adults
B29
25 crazy software bugs explained
American AccentBusiness EnglishUniversity StudentsWorking Adults
B29
Git Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
B25
There's a new Linux distro in town for developers...
American AccentBusiness EnglishUniversity StudentsWorking Adults
B25
The "vibe coding" mind virus explained…
American AccentBusiness EnglishUniversity StudentsWorking Adults
B24
Linux got wrecked by backdoor attack
American AccentBusiness EnglishUniversity StudentsWorking Adults
B24
7 Programming myths that waste your time
American AccentBusiness EnglishUniversity StudentsWorking Adults
C115
Nvidia CUDA in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
B23
OpenAI’s new browser feels familiar…
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
Meta's new model wants "deep access" to your personal life...
American AccentBusiness EnglishUniversity StudentsWorking Adults
✨ Aanbevolen Video
C17
67 zinnen
8 Most Important System Design Concepts You Should Know
Business EnglishUniversity StudentsWorking Adults
C13
156 zinnen
100+ Computer Science Concepts Explained
American AccentBusiness EnglishUniversity StudentsWorking Adults
C12
187 zinnen
How to ACTUALLY Get a DevOps Job in 2026
Business EnglishInterview EnglishUniversity Students
C11
54 zinnen
What is a server? Types of Servers? Virtual server vs Physical server 🖥️🌐
Business EnglishUniversity StudentsWorking Adults
C12
102 zinnen
What is Docker? Docker container concept explained || Docker Tutorial 1
Business EnglishUniversity StudentsWorking Adults
C11
78 zinnen
How I deploy serverless containers for free
Business EnglishUniversity StudentsWorking Adults
C11
78 zinnen
The easy way to keep your repos tidy.
Business EnglishUniversity StudentsWorking Adults
C11
423 zinnen
Free CCNA | VLANs (Part 2) | Day 17 | CCNA 200-301 Complete Course
Business EnglishUniversity StudentsWorking Adults
C130 zinnen
7 Phases of Penetration Testing Explained | Think your system is safe? #cybersecurity #pentesting
Business EnglishUniversity StudentsWorking Adults
C13
13 zinnen
Robots with connected brains
Business EnglishUniversity StudentsWorking Adults
C11
74 zinnen
LangChain in 5 Minutes (Explained Clearly)
Business EnglishUniversity StudentsWorking Adults
Woordenschat en spreektips bij deze les
Deze video bevat 105 zinnen en 1837 woorden om na te spreken. Het gesproken deel duurt 8:27. De spreker praat snel, ongeveer 217 woorden per minuut, dus reken op verbonden en ingeslikte klanken. Slechts 79% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden, dus de woordenschat is pittig.
Belangrijke woorden in deze video
15 woorden uit de video die het leren waard zijn, met uitspraak en betekenis:
| Woord | Uitspraak | Betekenis |
|---|---|---|
| container zelfstandig naamwoord | /kənˈteɪ.nəɹ/ | bak |
| server zelfstandig naamwoord | /ˈsɝvɚ/ | server |
| cloud zelfstandig naamwoord | /ˈklaʊ̯d/ | wolk |
| instruction zelfstandig naamwoord | /ɪnˈstɹʌkʃən/ | onderwijs |
| desktop zelfstandig naamwoord | /ˈdɛsktɒp/ | desktop |
| layer zelfstandig naamwoord | /ˈleɪ̯ɚ/ | laag |
| install werkwoord | /ɪnˈstɔl/ | installeren, aansluiten |
| database zelfstandig naamwoord | /ˈdeɪtəˌbeɪs/ | database, databank |
| disk zelfstandig naamwoord | /dɪsk/ | schijf |
| execute werkwoord | /ˈɛksɪˌkjuːt/ | executeren |
| directory zelfstandig naamwoord | /dɪˈɹɛktəɹi/ | gids, repertorium |
| package zelfstandig naamwoord | /ˈpæk.ɪd͡ʒ/ | pak |
| solve werkwoord | /sɒlv/ | oplossen |
| remote bijvoeglijk naamwoord | /ɹəˈməʊt̞/ | verwijderd, afgelegen |
| developer zelfstandig naamwoord | /dɪˈvɛləpɚ/ | ontwikkelaar, ontwerper |
Phrasal verbs die je zult horen
| Woord | Uitspraak | Betekenis |
|---|---|---|
| go down werkwoord | afdalen | |
| point out werkwoord | aanwijzen, aanduiden | |
| shut down werkwoord | afsluiten, uitzetten | |
| slow down werkwoord | afremmen | |
| start up werkwoord | /stɑɹˈtʌp/ | opstarten |
Uitspraak om op te letten
De spreker gebruikt 18 samentrekkingen en verkorte vormen, zoals we're, you'll, you're. Spreek ze kort uit, zoals je ze hoort.
- De klanken “sh” en “zh”: instruction /ɪnˈstɹʌkʃən/, allocation /ˌæl.əˈkeɪ.ʃən/, extension /ɪkˈstɛnʃən/, efficient /ɪˈfɪʃənt/, congratulations /kənˌɡɹæt͡ʃəˈleɪʃ(ə)nz/
- Lange woorden — let op de klemtoon: 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/
Zo oefen je met deze video
- Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
- Begin op 0,75× snelheid, spreek zin voor zin na en ga terug naar normale snelheid zodra het makkelijk gaat.
- Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als container, server, cloud.
Grammatica in deze video
De structuren die de spreker het meest gebruikt, met de exacte woorden uit de video:
| Structuur | In de video |
|---|---|
| Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doet | is delivered · is called · are often broken |
| Betrekkelijke bijzinnen who / which + zin — extra informatie over een persoon of ding | servers, which are · stateless, which means · colon, which is |
| Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog telt | has actually changed · has finally come · we've looked |
Wat is de Shadowing-techniek?
Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.