1 00:00:04,900 --> 00:00:08,740 Now we are running both front end and FBI in different containers. 2 00:00:08,950 --> 00:00:13,930 Here was container for front end application and here was container for API service. 3 00:00:14,530 --> 00:00:18,100 Now let's go inside of the image, just give you a front and container. 4 00:00:18,310 --> 00:00:21,940 By using the name of the container, in my case, ISIS's name. 5 00:00:21,940 --> 00:00:23,590 Here it is again random. 6 00:00:23,590 --> 00:00:26,590 And in your case, this name will be completely different. 7 00:00:26,890 --> 00:00:30,490 So please grab this name and let's open up in your tap. 8 00:00:30,490 --> 00:00:32,560 And here, let's enter Docker. 9 00:00:32,560 --> 00:00:34,570 Accept this idea. 10 00:00:34,870 --> 00:00:37,450 Name of the container and here was the best. 11 00:00:37,660 --> 00:00:38,500 We are opening. 12 00:00:38,600 --> 00:00:42,700 Canals have brought us in the run in container and this vast shell process. 13 00:00:43,060 --> 00:00:49,090 And unfortunately, I see your error exec best executable file not found in your site path and that 14 00:00:49,330 --> 00:00:54,160 that best executable is not available in this Node.js container. 15 00:00:54,610 --> 00:00:55,090 This way? 16 00:00:55,120 --> 00:00:59,410 Let's try and also sell and at this stage, sell shortly. 17 00:00:59,420 --> 00:01:00,460 Shot like that. 18 00:01:00,850 --> 00:01:01,660 Let's try that. 19 00:01:02,290 --> 00:01:08,200 And now I'm inside of the container command prompt looks a bit different from the vessel, but we're 20 00:01:08,200 --> 00:01:11,620 able to perform similar actions as we did using best. 21 00:01:12,070 --> 00:01:16,480 For instance, if I leased files and folders here, I don't see such files as package. 22 00:01:16,480 --> 00:01:22,390 The JSON package dislodged the JSON, and all those files are located inside of the app folder. 23 00:01:22,510 --> 00:01:24,220 It is our working directory. 24 00:01:24,940 --> 00:01:31,000 If I go one level up and list files and folders here, I'll see actually different files in the root 25 00:01:31,000 --> 00:01:33,130 of the file system in this container. 26 00:01:33,370 --> 00:01:40,240 It is running our front end application and I see here or similar folder as we've seen in Python container 27 00:01:40,390 --> 00:01:43,230 and they are home Mendeleev and so on. 28 00:01:43,810 --> 00:01:46,480 And along with them, I see up folder here. 29 00:01:46,660 --> 00:01:49,690 Where are we placed all our application files? 30 00:01:50,350 --> 00:01:57,010 OK, let's go back to our folder and here in this folder now I see Load Modules folder and this folder 31 00:01:57,010 --> 00:02:00,460 was created by npm at this build. 32 00:02:00,490 --> 00:02:08,199 Step one NPM Install this the silent because we installed all our front end application dependencies 33 00:02:08,320 --> 00:02:12,390 inside of the image after copying package and package. 34 00:02:12,400 --> 00:02:13,810 This logged the Jason files. 35 00:02:14,470 --> 00:02:21,130 This way, here inside, we now see node modules folder, and this way we are actually able to run our 36 00:02:21,130 --> 00:02:26,740 React application here because all necessary dependencies are located inside of the container. 37 00:02:26,950 --> 00:02:28,660 And here you clearly see that. 38 00:02:29,690 --> 00:02:34,520 Let's now have a look at the processes that are running inside of the container by entering the command 39 00:02:34,970 --> 00:02:38,690 and Root Broads was started using npm start command. 40 00:02:39,350 --> 00:02:47,360 And this process was defined by some deconstruction here in the Docker file, npm start and beom start 41 00:02:47,360 --> 00:02:48,230 has started. 42 00:02:48,230 --> 00:02:50,360 Child brought us react scripts. 43 00:02:50,360 --> 00:02:55,220 Stop this actually that brought us that started our React application. 44 00:02:55,790 --> 00:03:00,890 Also, there was another process called Sha and this that brought us that we actually started in order 45 00:03:00,890 --> 00:03:04,970 to open this interactive shell to the running container. 46 00:03:05,630 --> 00:03:06,980 And we just entered P. 47 00:03:06,980 --> 00:03:08,170 S Command this way. 48 00:03:08,180 --> 00:03:10,580 Here we see one more brought to Scorpius. 49 00:03:11,510 --> 00:03:17,240 This whole file system and this whole process does look like inside AWS, a run container, and this 50 00:03:17,240 --> 00:03:21,590 front end container is completely separated from the back and API container. 51 00:03:21,980 --> 00:03:25,420 All right, let's exit from this source shell now. 52 00:03:25,430 --> 00:03:26,600 Very important point. 53 00:03:27,080 --> 00:03:34,220 Remember that before actual built broaddus of the front end image, I asked you to remove node modules 54 00:03:34,220 --> 00:03:39,950 folder and we removed it in our front and folder in the Images Gallery project. 55 00:03:40,490 --> 00:03:46,700 And now, if you refresh for the rows here, I'll see that node modules folder is absent in the front 56 00:03:46,700 --> 00:03:47,410 and folder. 57 00:03:47,420 --> 00:03:52,490 I don't see it, but inside of the container there is node modules folder. 58 00:03:52,490 --> 00:03:53,540 We just verify that. 59 00:03:54,170 --> 00:04:00,050 And after the small pause, let me explain to you why you should have both node modules folder here 60 00:04:00,050 --> 00:04:04,910 inside of the front and folder in your project and inside of the container. 61 00:04:05,360 --> 00:04:07,280 Let me talk about that after the small box.