Now we are running both front end and FBI in different containers.
Here was container for front end application and here was container for API service.
Now let's go inside of the image, just give you a front and container.
By using the name of the container, in my case, ISIS's name.
Here it is again random.
And in your case, this name will be completely different.
So please grab this name and let's open up in your tap.
And here, let's enter Docker.
Accept this idea.
Name of the container and here was the best.
We are opening.
Canals have brought us in the run in container and this vast shell process.
And unfortunately, I see your error exec best executable file not found in your site path and that
that best executable is not available in this Node.js container.
This way?
Let's try and also sell and at this stage, sell shortly.
Shot like that.
Let's try that.
And now I'm inside of the container command prompt looks a bit different from the vessel, but we're
able to perform similar actions as we did using best.
For instance, if I leased files and folders here, I don't see such files as package.
The JSON package dislodged the JSON, and all those files are located inside of the app folder.
It is our working directory.
If I go one level up and list files and folders here, I'll see actually different files in the root
of the file system in this container.
It is running our front end application and I see here or similar folder as we've seen in Python container
and they are home Mendeleev and so on.
And along with them, I see up folder here.
Where are we placed all our application files?
OK, let's go back to our folder and here in this folder now I see Load Modules folder and this folder
was created by npm at this build.
Step one NPM Install this the silent because we installed all our front end application dependencies
inside of the image after copying package and package.
This logged the Jason files.
This way, here inside, we now see node modules folder, and this way we are actually able to run our
React application here because all necessary dependencies are located inside of the container.
And here you clearly see that.
Let's now have a look at the processes that are running inside of the container by entering the command
and Root Broads was started using npm start command.
And this process was defined by some deconstruction here in the Docker file, npm start and beom start
has started.
Child brought us react scripts.
Stop this actually that brought us that started our React application.
Also, there was another process called Sha and this that brought us that we actually started in order
to open this interactive shell to the running container.
And we just entered P.
S Command this way.
Here we see one more brought to Scorpius.
This whole file system and this whole process does look like inside AWS, a run container, and this
front end container is completely separated from the back and API container.
All right, let's exit from this source shell now.
Very important point.
Remember that before actual built broaddus of the front end image, I asked you to remove node modules
folder and we removed it in our front and folder in the Images Gallery project.
And now, if you refresh for the rows here, I'll see that node modules folder is absent in the front
and folder.
I don't see it, but inside of the container there is node modules folder.
We just verify that.
And after the small pause, let me explain to you why you should have both node modules folder here
inside of the front and folder in your project and inside of the container.
Let me talk about that after the small box.