Docker Compose #0002

I used this git repo in this session.

AI Generated Transcript

So hey guys, we are running this live teams meeting and it's also being streamed right now.
Let's go test whether the stream is successfully working. I think it is and so let's go test it out
on LinkedIn. Is my stream live? I think I got a notification on yeah it is live.
So that's the live stream. And let's see on Twitter. We should be live on Twitter as well.
Here we go. So notifications on my profile. We should be seeing a live stream of us talking.
Like that's where we should show up. So there it is. And so this is the live stream happening
on Twitter as well. And so I'm not interested in seeing the live stream, but it's very
interesting our meeting. So that's what we're doing. So let's recap. What are we discussing?
Docker. I have this Macintosh in my hand. And I want to connect it to a Linux machine.
That address of that machine is 192.168.1.10. It is an iMac.
And it is in the same room that I have, so I can locally SSH into it.
And this machine has Docker installed and EOCKER. That's where I will be experimenting.
So for this experimentation today, we will discuss Docker and Docker Compose.
And I have a Git repository already prepared. I will give you a link to that so you can actually
use it. And I will also clone that Git repository locally onto this machine.
And using it will be a good demonstration of what Docker Compose is and how you can put
things together to construct a variety of applications and run them in Docker containers
plurality, like more than one. So multiple containers coming together to form what is
needed as an architecture for your given application. That's the design point.
So we are looking about talking about a Git repository. I have that repository with me.
I will open up a browser and show you that repository and also tweet it out so you can
access it. So here I go open my browser and go to GitHub. And
here in GitHub, I will have to go look for it. So the repository is in my company account
where the thing is called Docker files. I think that's the
repository. No? Yes. Yeah, that's the name. So I'm going to go there, Docker files.
And this is a public open repository so anybody on the planet can access it. So there it is.
That's the repository. I'm going to grab that code link, copy it, and then use that link to clone the
whole thing locally into this iMac, the machine that is running Ubuntu. By the way, this iMac
is not a Mac. It's just the machine is Mac. It used to be Mac like a few years ago.
Now it is running Ubuntu. So that is where I want to bring this Git repository and put it right there
on this box. So let's go there. Terminal. And right now this is the Macintosh.
You can see it. Now I'm going to SSH into the machine, the iMac. I SSH. Now you see that this
is an Ubuntu machine. And there I already have this thing Docker files cloned. So I don't want
to use it. What I want to do is remove that folder called Docker files, which I cloned yesterday.
So I'm going to remove it. And so apparently permission denied because I was like running
something running there. So I'm going to go clean it out completely. So sudo rm-rf Docker files. And
it should die. It died. Now nothing is there on that folder because the folder itself is cleaned
out. So what I want to do next is make it bigger and then git clone. So it comes down. The folder
containing the entire repo is now available to me in this location, Docker files. And that's the
folder. Here you can see inspect the contents of the folder. So there are exercises here that I
will be doing live that will explain what is Docker Compose and how we can put things together to run
a multiple container application structure. And we can use buzzwords about end tier architecture
and all the buzzword bingo. I don't do buzzwords. Absolutely no buzzwords in my talk. I talk simple,
plain, but get things to work. That's the idea. So this is the folder we are looking at.
And I want to go to that folder so that you can see it in a visual fashion for which I will be using
a visual editor. So here it is, VS code. Actually, this is not VS code. So what Microsoft does
is they snoop and look at what your activities are and they monitor you.
So that is a bad behavior, so I don't like that. So what I do is, actually what many people do
is they have forked this thing called VS code and they have created a thing called VS code M.
So I'll tell you about VS code M. Here it is VS code M. This is actually the open source clean
version of VS code. Open source libre, like open source as in no monitoring, no Microsoft nonsense,
clean, genuine, open software, which has no relationship with Microsoft. That's what VS code
M is. It's basically VS code. VS code is open source by Microsoft, but many people have
contributed. Many people have modified VS code to create this thing called VS code M, and it is
a very good product. Why? Because Microsoft would not know what we are doing. If you open VS code,
they will know certain things. I don't want anybody to know what I'm doing, unless I'm
disclosing it. So privacy is important to everybody, including you and me. So we are using VS code M.
So not VS code, code M. Slightly different, very, very similar. Everything works just like that,
but Microsoft does not come in the way. Nobody comes in your way. That's the underlying concept
of freedom. So when I talk about free, I actually think of it as a free environment.
Free means freedom, not zero dollars. That's not what I mean. Free means freedom, and that's what
this thing gives me, open source. So VS code M is what I am running, and there I am going to connect
to that machine, which I told you about like that, and then hook it up. So this is a VS code M
connection, remote connection to that computer that I told you about, and there it is. So you can now
look for that folder that I cloned, and it is, what was it, Docker files, something there.
So that's the folder. If you can see it bigger, a little bit better. I think that's better. So here's
the folder called Docker files, and in there you can also, by the way, locally clone. If you have
a computer with you, you can clone it, and you can see it. And what I will do now is in that folder,
by the way, this is the same machine that I was talking about. You name iMac. The same iMac is
what contains that folder called Docker files. Same thing. That contains the same exact thing.
We are now remotely connected through VS code M into the machine, and we have the files here.
So the reason I do it this way is so I can actually look at the step-by-step instructions
and show it to you, and then follow along so you can understand what's going on.
And this is basically a hands-on exercise. Everything I try to do is hands-on, and it's
written down in some Git repo, and we'll actually execute instructions. That's the idea. So having
said that, let's do it. So step-by-step. Here is this part one, like the first step. The first step,
in that first step, what we have, let's get rid of these browsers. So browser window closed.
Don't want this. I think you need to tweet this out. I'm going to tweet this link.
Tweet that with the reply, I am using this repo today. And tweet. So people will know.
And so people who are looking, they might see it.
Okay. And next, what I want to do is run these steps that we have. So in our step-by-step folder,
we have this file called one. That one, file number one, that file. It has written instructions
that only I can interpret and understand because it's not very nicely written. But I know what I
wrote, so I can explain it to you. The first thing, A and B are equivalent. What I mean by that
is this step A, that I highlighted in blue color, is very, very similar, actually identical,
equivalent to the step B here. It's basically the same thing. What do I mean to tell you
is that this is execution of docker-compose on the command line. Whereas the B section,
Nilesh, here B, these two commands, one at a time. So one and two. So two separate commands
versus this command. Nilesh, can you hear me for a second?
Yes. Yes, Sanjay. Hi. How are you? Yeah. Yeah. Good. Good. Hey, Nilesh, can you,
I think, first of all, I'm getting your screen cut off in the left-hand side and the right-hand
side, all the participants are getting displayed. So half of the thing is basically that participant
the screen is taking. So I know that's a problem with teams. So I don't know how to fix that
participation videos. You have shut off your videos, which is nice. No, no, no, no. But you
still see the circles, right? You still see circles. No, you just, I think, show participant
or if you remove show participant on your side, then those will go away. Only your screen will be.
I understand. I just don't know where the button is. Can you tell me?
Oh, no, I'm a participant. So I get that. I think it's better now. I think whatever I did,
but half of the screen is taken by those participants and half of the screen is
only displayed. So I made you a presenter and can you modify it to suit what you need?
Okay. Oh, you made me a presenter. Yeah, I made you a presenter. So see if you can modify. I just
don't know how to hide other people's circles, right? That's what I see coming in the way on
the right side. Is that what you tell me? Yeah, but that's okay. I think my