1
00:00:04,380 --> 00:00:10,170
Now we are running both containers front and container and a service container in different depths here.

2
00:00:10,710 --> 00:00:15,420
And then this load to look and demonstrate to you how you are able to run containers in detached mode.

3
00:00:15,900 --> 00:00:19,140
Let's hope both containers bypass and key combination control.

4
00:00:19,150 --> 00:00:21,690
See zero for front and application.

5
00:00:22,230 --> 00:00:26,250
Docker container will stop and let's stop API container.

6
00:00:26,490 --> 00:00:29,310
Similarly, as we did four front and container control.

7
00:00:29,310 --> 00:00:29,610
See?

8
00:00:30,570 --> 00:00:31,680
Container will stop.

9
00:00:31,920 --> 00:00:38,990
And if I leased containers now Docker bills, I will see no containers that account Iran and no less

10
00:00:39,010 --> 00:00:43,250
Iran, both front and container and API container in the.

11
00:00:44,190 --> 00:00:51,360
Using this D option and notice that now you could run Docker containers anywhere in any path.

12
00:00:51,660 --> 00:00:56,220
You don't need necessarily to see to API or front and folder.

13
00:00:56,430 --> 00:01:01,380
I could even see, for instance, to use a home directory and Ron Docker containers here.

14
00:01:02,100 --> 00:01:05,340
Docker run this option with exports.

15
00:01:05,370 --> 00:01:08,160
Same as before 50 50 for API.

16
00:01:08,160 --> 00:01:13,950
A service and container port is saying 50 50 and next, let's at best option.

17
00:01:13,950 --> 00:01:19,230
The best and afterwards will be name of the Image Images Gallery.

18
00:01:19,950 --> 00:01:23,310
This API let's run this first container.

19
00:01:23,940 --> 00:01:25,470
No, here in this output.

20
00:01:25,470 --> 00:01:29,610
After such command, I see success of the container that was started.

21
00:01:30,450 --> 00:01:37,120
And if I enter Docker voice command, I see that now there is container running and then similar weight.

22
00:01:37,140 --> 00:01:42,030
Let's run one more front and container Docker run DSP.

23
00:01:42,300 --> 00:01:46,200
Now we export port three thousand to the same port three thousand.

24
00:01:46,620 --> 00:01:49,230
Let's also add this deep detection option.

25
00:01:49,630 --> 00:01:50,970
Images Gallery.

26
00:01:51,450 --> 00:01:56,400
Front end loaders name of the image for front end container.

27
00:01:57,060 --> 00:01:57,750
Let's run it.

28
00:01:59,110 --> 00:02:02,320
Also, a showcase of the newly created container.

29
00:02:02,410 --> 00:02:03,040
Here it is.

30
00:02:03,670 --> 00:02:06,970
And now I should see two containers up and running.

31
00:02:07,240 --> 00:02:07,930
Here they are.

32
00:02:08,590 --> 00:02:14,950
Here are names that were generated for new containers because those containers are brand new containers

33
00:02:15,670 --> 00:02:17,120
previously around containers.

34
00:02:17,140 --> 00:02:23,200
Arnold stopped, and now I'm able to verify whether our front end service works as before.

35
00:02:23,590 --> 00:02:26,190
Let's go to web browser and refresh page here.

36
00:02:27,040 --> 00:02:33,070
Notice that you need to wait a bit until you'll see actually result in a web browser because npm start

37
00:02:33,070 --> 00:02:40,420
actually along with just script executable and it creates development, react, build and it takes some

38
00:02:40,420 --> 00:02:40,780
time.

39
00:02:41,380 --> 00:02:43,510
All right, Page was finally loaded.

40
00:02:43,720 --> 00:02:47,530
And no, let's try to search for some image, for instance, laptop.

41
00:02:48,770 --> 00:02:56,630
And a good result, it means that our back and EPA service works as well, and now we are running both

42
00:02:56,630 --> 00:02:58,460
containers in the test mode.

43
00:02:58,760 --> 00:03:04,460
And no, here in the terminal, you could perform other actions while containers are still running the

44
00:03:04,460 --> 00:03:04,910
ground.

45
00:03:05,570 --> 00:03:09,920
Let me now demonstrate to you how you could stop one of the containers if you want to do so.

46
00:03:10,340 --> 00:03:11,690
Let's, for instance, stop.

47
00:03:11,850 --> 00:03:16,460
Image Gallery API, a container with such name affectionate hoover.

48
00:03:16,760 --> 00:03:19,670
Let me take this name and run following command.

49
00:03:20,150 --> 00:03:24,500
Docker stop and hero based the name of the container.

50
00:03:24,620 --> 00:03:28,640
The discount Iranian Docker has stopped corresponding container.

51
00:03:28,820 --> 00:03:33,470
And if I enter Docker as now, I should see only one front and container.

52
00:03:33,950 --> 00:03:38,720
I could run stopped containers again by using Docker Start Command.

53
00:03:38,870 --> 00:03:42,560
And here will be the name of the stop container Docker start.

54
00:03:43,740 --> 00:03:44,970
Container will start it.

55
00:03:45,060 --> 00:03:48,410
Let's have a look at least of county run containers and the gain.

56
00:03:48,420 --> 00:03:49,380
There are two of them.

57
00:03:49,680 --> 00:03:52,520
Front end and API great.

58
00:03:52,800 --> 00:03:58,170
This how you could run containers in the taste mode in background and the similar way you could run

59
00:03:58,170 --> 00:04:00,230
all the containers if you want to do so.

60
00:04:00,990 --> 00:04:06,480
Also notice that if you want to have a look at logs of specific containers because actually we don't

61
00:04:06,480 --> 00:04:11,940
see any output, you could do so by using the following command Docker logs.

62
00:04:12,930 --> 00:04:15,930
And here will be the name of the container, for instance, this one.

63
00:04:17,070 --> 00:04:17,610
Like that?

64
00:04:18,269 --> 00:04:22,200
And here are logs that were generated by our front and container.

65
00:04:22,740 --> 00:04:27,150
Similarly, you could have a look at the logs of and a container, for instance this one.

66
00:04:27,300 --> 00:04:30,000
Let me quote this name Docker logs.

67
00:04:30,390 --> 00:04:35,190
Paste this name here and now I see logs from the flask application.

68
00:04:35,820 --> 00:04:41,250
No, you don't required to run the front end and the day of service somewhere else separately in different

69
00:04:41,250 --> 00:04:42,640
tabs using Docker.

70
00:04:42,660 --> 00:04:45,570
You could very easily run both services in the background.

71
00:04:46,500 --> 00:04:48,750
For now, we're done with this first step.

72
00:04:48,780 --> 00:04:53,130
We created Docker files both for front end and API applications.

73
00:04:53,640 --> 00:05:00,090
And now we are moving to the next step and we will adopt Docker compose and we will use it in order

74
00:05:00,090 --> 00:05:05,550
to start front end and API services simultaneously using just one command.

75
00:05:06,420 --> 00:05:13,290
And afterwards, we will extend Docker Compose set up and we will add such containers as Maunga and

76
00:05:13,290 --> 00:05:19,110
Mongo Express, and all those containers will be stored only using one command.

77
00:05:19,590 --> 00:05:20,940
And this beauty of Docker.

78
00:05:21,330 --> 00:05:27,750
So let's next at Docker compose file and at local instructions for starting front AMP and API containers.

79
00:05:28,110 --> 00:05:29,640
I'll see you guys just in a bit.