ID: RISE 2020.4.10.4 In today's session I learned the following: * There is a lot of wastage of memory and resources in case of bare metal OS installation because it reserves all the resources * Some of the drawbacks of bare metal are resolved by Virtualization but virtualization also has some drawbacks like it creates a separate copy of kernel for every OS installation * Drawbacks of both bare metal and virtualization are resolved by docker * I learned about docker architecture and how it works based on Docker engine * Docker engine is also called docker host and whenever any OS is launched in Docker it does not make separate hardware resources for all OS * Command "pstree" is used to know the process tree of OS * Actual reason why systemctl does not work in docker is because it does not have systemd process running and systemctl requires systemd process to be running * Got to know more about private and public IP * About SNAT (Source NAT) and DNAT (Destination NAT) * What is working of host network type in Docker network

Synopsis -learnt core concepts and architecture of docker engine. - learnt deep about virtualization containers bare metal -learnt NAT PAT and networking work flow.

In this session I learned about -- architecture of docker, NAT and PAT, docker engine, docker internal cmd, docker port mapping, public ip and private ip, basic docker cmd, bare metal and virtualization, about SNAT and DNAT, PStree... THANK YOU SIR 😊

In this session of Docker, we learned the following things:- -- Architecture of docker -- how bare metal works -- Memory wastage in bare metals because of reserved resources -- learned and compared docker with virtualization and why docker is fast -- IP addresses(public and private) -- limitations of virtualization -- learned about docker engines and docker drivers -- some commands like pstree see the process tree of OS and uname-r check the kernel in docker, rpm -q kernel -- Learned about SNAT(Source NAT) and Destination NAT, PAT and the workflow of Networking -- Finally concluded why docker is fast and the session helped us to revise our Dcoker commands as well. Thank You for this great session Sir

Session's Summary: * Learned about docker architecture * About Docker engine * bare metal and virtualization * Public ip and private ip * About SNAT and DNAT

I have learnt the basics of docker architecture, core commands of docker, about docker engine,bare metal and virtualisation,about SNAT and DNAT , public IP and private IP etc.

Today I learnt about docker architecture, docker engine, public IP and private IP, learnt deep about about virtualization containers bare metal, NAT PAT and networking work flow.

In this session, I learnt about the architecture of Docker and public and private IP among many other things.

The session was good and I learned so many new things like: 1. learned about the architecture and engine of docker on which it works. 2. learned how the concept of bare metal and virtualization in detail,how they come into picture and its drawbacks. 3. learned about the networking concepts like pat,dnat (destination nat),snat (source nat) etc. 4. learned about the working of host network in docker and also about private and public IP. 5. learned about the docker mapping. 6. learned many commands like: pstree, ps -aux, and many more things... Your work is highly appreciated. Thank you for giving your precious time and making our country a nation of creators. RISE id : RISE 2020.83.8.1

we saw that how all the other system or the os running platform are of less useful or fast like the bare metal system or the virtualization, they are slow and takes enough time to set up and the docker is a great solution to it. we learnt about the docker engine that it makes the docker work. learnt about process of tree of OS pstree command, learnt about source NAT and destination NAT

today we started with basics of docker architecture and docker engine. Then we learned about bare metal and virtualization, public and private IP. and moved to SNAT and DNAT

In this session i learned about Docker port mapping,docker network,architecture,pstree,ps-aux, national and pat 2020.70.7.1

We learned about Docker engine, docker architecture, bare metal and virtualization, public IP and private IP, SNAT, DNAT and PAT. Space management, core networking concept, host concept etc

RISE 2020.10.12.2 we have learned about virtualization and docker architecture and also we get knowledge about engine and drivers and hypervisior.

learned about what is really virtualization is , what is docker architecture, and a lot about networking how public and IP works. about the bridge and host networks too.

Hello sir, I learned about docker architecture, about docker engine, bare metal and virtualization, and about SNAT and DNAT

Yes, missed live sessions but learned from offline video.

I learned about Docker architecture Public IP and private IP Bare metal and virtualization

I had learn in our 4 session of docker is : *about docker engine, architecture, docker port mapping, some basic docker command, docker network, internal docker concept, use case of an docker, how to open app in docker container *about bar metal and virtualization *public and private ip *about SNAT and DNAT *Pstree, ps-aux

RISE 2020.10.7.1 - Today I learnt about the docker architecture and docker engine, wastage of memory, about bare metal and virtualization, few commands and concepts of DNAT, SNAT, and PAT.

in this i learned about 1. docker architecture 2. docker engine 3. hypervisor 4. bare metal installation 5. about public and private op

I learned about - use cases of docker - internal docker

id- RISE 2020.4.5.5 learnt about docker architecture and engine, bare metal and visualization

RISE 2020.7.2.1 From today's class i have learnt about docker architecture and also about docker engine and learn about virtualization and bare metal and got to know about public and private ip and also about snat and dnat.

In this session we learned about docker architecture, concepts about Docker engine, concept of bare metal and virtualization, public and private ip , also learnt about SNAT and DNAT

Today vimal sir taught us about the wastage of memory , docker architecture, docker engine ,virtualization ,about NAT,SNAT,DNAT,PAT ID-RISE2020.74.1.4

We learnt about docker architecture, bare metal, public and private ip and about snat and dnat

RISE 2020.62.2.5 In today's session we learnt about docker engine architecture , about virtualization and bare metal concept I.e.,how it actually consumes space and memory , got to know about private and public IP address , 3- docker driver i.e., DNAT, SNAT and PAT, also learnt about PSTREE cmd .

Session summary is as follows... Firstly we learned about docker architectures... then about docker engine...We studied about bare metal and virtualization... Public IP and private IP and about SANT and DNAT... THIS WAS A VERY FUN CLASS

In this session, I learnt -docker architecture -docker engine -bare metal and virtualization SNAT and DNAT

In this session i learnt: wastage of memory and resources in bare metal OS, docker architecture, docker engine, NAT, SNAT, DNAT, PAT, drawbacks of virtualization, Pstree command, ps -aux command, docker network, etc ID: RISE 2020.8.18.1

Rise id - 2020.15.13.1 This session got me introduced to -Working of containers and vms -Kernels -Internal architecture of docker -Types of ips and its assigning -DNAT and SNAT -What is PATing -Systemd process, parent and child -process -Host networking in docker -Why docker starts an os so quick

In this session I learnt, Docker architecture and engine Bare metal and virtualisation About NAT, SNAT, DNAT, PAT Private and public Ip Pstree, ps - aux commands

In this session we learned about the architecture of docker, docker engine,concept of virtualization, bare metal,SNAT and DNAT.

In this session we have learnt about that we can't lanch second os parallely as os boots take overall control of all hardware , we can solve draw drawbacks through virtualizations , docker architecture and Engine , limitations of virtualisation , SNAT(source NAT) DNAT(destination NAT) , command pstree, uname-r , container engine docker drivers , (public) ip and (private) ip can't ping each other and NAT and PAT concepts.

in this session i have learnt about:- -docker architechture, docker engine, public ip and private ip and snat and dnat

In this session I learnt about : * architecture of the docker * Docker engine * Public and private IPs * SNAT and DNAT

This session i learn about docker architecture and deep virtualization,DNAT and SNAT and core conpect of sharing main component of basesystem to Docker etc.

IN THE SESSION I UNDERSTAND THE FOLLOWING POINTS. 1) docker architecture 2)learn about bare metal 3) docker engin 4) working of host network type in docker network 5) know more about private ip & public ip 6) command " pstree" is use to know the process tree of os 7)learn about SNAT & DNAT 8) learn about NAT & PAT 9) drawback of both base metal & vertulization 10)whe I hypervisor

In today’s session I learned about basic commands of docker like NAT,PAT,pstree and ps -aux.About architecture of docker.Bare metal and virtualisation.Docker port mapping -p option.

In this session we learned about docker architecture, docker engine, virtualization, hypervisor, hardware virtualization, public IP and private ip

learnt about kernel , dnating, snating, nating, pating, learned about ips that is public ip and private ip and bare metal and virtualization etc

In this session, I learned about: 1. Architecture of Docker 2. The Docker engine 3. Concept of Base metal 4. Virtualization 5. Networking - Public and Private IP addresses 6. Docker drivers like- DNAT, SNAT and PAT. 7. Kernel and resource utilization concepts

Summary 1)In this session i learn about architecture of docker also about its engine and its drivers 2)also learn about NAT,SNAT,DNAT,PAT. THANKS SIR

RISE 2020.16.28.2 I learned about.. 1. The architecture of the docker.. 2. Architecture of virtualization and bare - metal 3. How to work with host driver 4. Some of the linux commands in docker 5.docker engine 6. Also learned about SNAT DNAT and PAT.. 7. About ip... i. e public and private

In this session we have learnt about bare metal ,virtualization, docker engine ,public and private ip ,architecture, nat dnat concepts etc

In this session, I have learned about - -architecture of docker -docker-engine -public and private IP -snat and dnat -about virtualization RISE 2020.13.7.4

RISE 2020.7.4.5 In this session we learned about docker architecture and why we prefer docker, docker engine, about systemctl cmd, SNAT and DNAT, private and public IP.

sorry for watching late video but now i am watching carefully and with practical. I have learn Check information about Package, Check kernal version, Find software name, Check kernal in container, Wich kernal is use, All the process run in the os & how much memory use, PAT, Host driver. But I could not attend DOT workshop.

RISE2020.25.8.5 In this session we learned about following things .learned about docker architecture and many things about docker engine about bare metal and virtualization about public and private ip about SNAT AND DNAT

In the previous session we learned about:- ->There is a lot of wastage of memory and resources in case of bare metal OS installation because it reserves all the resources. ->Some of the drawbacks of bare metal are resolved by Virtualization but virtualization also has some drawbacks like it creates a separate copy of kernel for every OS installation . ->Drawbacks of both bare metal and virtualization are resolved by docker . ->I learned about docker architecture and how it works based on Docker engine . ->Docker engine is also called docker host and whenever any OS is launched in Docker it does not make separate hardware resources for all OS . ->Command "pstree" is used to know the process tree of OS . ->Actual reason why systemctl does not work in docker is because it does not have systemd process running and systemctl requires systemd process to be running . ->Got to know more about private and public IP . ->About SNAT (Source NAT) and DNAT (Destination NAT) . ->What is working of host network type in Docker network.

Last session explained docker architect, start from bare-metal, virtualization and docker architecture. also example how to exactly docker work and networking with docker such as NAT, SNAT, DNAT, PAT and finally Host Driver in docker networking etc.

According to me,i learnt: 1.)bare metal and virtualization 2.)docker architecture 3.)docker engine 4.)public ip and private ip 5.)DNAT and SNAT

I learnt - 1. Docker Architecture. 2.Docker Engine 3.Bare metal and virtualization 4. About what is public ip and private ip. 5. SNAT and DNAT

RISE 2020.28.2.2 in this session I learned about 1.bare metal 2.about docker engine 3. public IP and private ip 4.SNAT 5.DNAT 6.about vritualization 7.docker architecture

In this session , I learned: -Docker engine and architecture - Public and private IP - Baremetal and virtualisation - NAT , SNAT , DNAT - memory management - drawbacks of virtualization

we learn about docker architecture docker engine metal visualisation public IP and private IP snat and dnat we learn this all concept thanku

>drawbacks of base metails can be resolved by virtualiztion and drawbacks of virtualisation can be resolved by docker >we learnt about docker architecture and all the types >quick knowledge of cloud computing >Docker engine is also called docker host and whenerver any os is launched in Docker it does not make separate hardware resources for all OS >About Docker engine >bare metal and virtualization command pstree,uname -r SNAT DNAT

"RISE 2020.13.13.1" I have learned about the architecture of docker, docker port mapping, engine of docker, network in docker, SNAT, DNAT and many commands etc

RISE 2020-46-6-1 On this session..I learnt *The Docker architecture *About Docker engine *Detailed explanation of Bare-Metal and Virtualisation. *Need of Containerisation or Docker *Mapping the port from container to Docker host *Concept of Networking things like SNAT, DNAT, and PAT *Public IP and Private IP

in this session we learnt about docker engine, command like pstree, umname-r also about 3 types of docker driver, NAT and PAT concepts, problems which we can fix by virtualization. id : RISE 2020 8.11.4

1-learnt about docker engine 2-learnt about public and private ip 3-learnt about architecture of docker 4-commands like ps -aux, pstree 5-learnt about why docker boots very fast 6-some concepts like DNAT,SNAT,and PAT

I have learned following things: 1)how memory is used in bare metal O.S installation. 2)we can resolve the problem of bare metal problem by using virtualization. 3)how docker resolve the drawbacks of virtaulization and bare metal installation. 4)learned about docker engine. 5)also learned about architecture of docker. 6)what is SNAT and DNAT. 7)the reason why systemctl cmd don't work in docker.

RISE 2020.15.18.3 - In this session I learned about docker architecture. - About docker engine. - then we know about bare metal and virtualization. - we know the public and private IP and difference between them. - About SNAT and DNAT. - basic commands like pstree, ps-aux etc. - then we know about host driver. etc Thank you

RISE 2020.44.12.2 I learnt about: docker engine docker architecture Networking like DNAT,etc virtualization ,etc

In this session we learned about - use cases of docker - virtualization - about SNAT & DNAT Kernal & ram can be shared within multiple os - learned about docker architecture

RISE 2020.9.37.5 I learnt in this session *Architecture of docker *About docker engine *Bare metal and virtualization os *Concept of networking---> NAT,SNAT,PAT

Rise 2020.16.22.3 In this docker session i have learnt about 》concept of bare metal setup 》virtualisation by hyper - visor software 》why industry go for containersation instead of virtualisation 》verify the kernel memory inside the docker using rpm -qa kernel ,uname -r and free m commands 》the reason behind the fast launching of docker container 》first process start when karnel loads and checking it in graphical by using pstree command 》 the reason why the systemcntl command failed inside docker 》got to know about publiv and private ip 》 how to connect both the ip private and public with the help of DNAT 》but first how to solve the DNAT issue with PAT and other way of aaccesing private IP from public IP using host driver! Thank you sir!

In this session I have learnt about following things:- 1) get to know about docker concepts, its engine and its architecture 2) learnt about bare metal. 3) some networking concepts like SNAT, DNAT, Pat, and some docker commands. 4) public and private ip 5) creation of network packet. 6) why systemctl doesn't work in docker . 7) what is working of host network type in docker network.

iiec id - RISE 2020.16.5.1 In this session i have learned about docker architecture and docker working based on Docker engine bare metal and virtualization , and how docker is better than Private and public IP Some commands like:- pstree, hypervisor, NAT, SNAT, DNAT and PAT

RISE 2020.50.2.1 From the session I learnt about about bare-metal how virtualization tech came Docker Architecture networking concepts like SNAT, DNAT AND PAT few commands

Session's summary: * We need an os for the interaction of hardware and software and we can run programs with the help of os. * Kernel scan all the hardwares and load the drivers when we launch an os. * Hypervisor: The software that allocates the machine resources to multiple os as per the user to provide complete utilization of those resources and this concept is known as virtualization. * Limitations of virtualization: we have to install kernel and load all the drivers everytime we launch os which is a wastage of resources. Containerization resolves the drawbacks of bare metal and virtualization. In containerization we have only applications inside the os and it shares the kernel, driver and other resources from the base os. The program on which this setup works is known as container engine. * unake -r command (command to show on which kernel the os is running). * Parent process is the first process to run when the kernel starts and it's PID is always equals to 1 (In rhel parent process is systemd). * pstree command * About packet, source IP and destination IP * SNAT (source network address transmission)- replacing source IP which router's public IP * DNAT (destination network address transmission)- replacing public IP with router's IP. * PAT (port address transmission) * Concept of host network driver

In this session I learn about the following things:- ->bare metal and virtualization -> About the docker Architecture ->Description of SNAT and DNAT ->Public ip and private ip ->"pstree" is used to know the process tree of OS ->About the docker Engine (docker host) ->About the reason why systemctl does not work in docker is because it does not have systemd process running Thanks for giving your crucial time sir🙏🙏🙏🙂

Hi Vimal Sir, I am very glad i found this training in youtube. I have one doubt. For example i have redhat 8 as my base OS and i have installed docker and launched centOS container with one small web application. I created image and pushed to repository. One of my colleagues pulled that image who is having windows as their base OS and installed docker on top of that. He pulled the image and tried to run and create container. will it work in the same way because my image was created on redhat8 base OS. One more doubt is what if my base OS is windows and i launched centOS containers. Here it can not use my base kernel right. How about of speed of launching the container in this case. My base OS and container OS is different. Please clarify my doubts if some one already know the answers. Once again thank you sir for this wonderful training. Looking forward to be part of your training's from here on

RISE 2020.7.12.3 Today we learn about concepts related to architecture of docker, docker engine , docker driver, discuss and learn deeply about bare metal and virtualization related with docker and OS, discuss and learn about NAT (SNAT , DNAT), PAT, discuss about ip (private , public).

I learn about how wastage of memory and resources in bare metal OS installation, drawbacks of virtualization, docker architecture docker engine, docker host, the concept of systemctl, knowing more about private and public IP, and learn about SNAT and DNAT, working of the host network, pstree comaands.

Today's session summary :- 1. So the prime focus of this lecture was the discussion on architecture of docker based on the basic link of virtualization technology and container technology. 2. Basic internal working of docker engine. 3. About kernels and drivers in docker. 4. We also learned about the limitations of virtualization and benefit of containerization on it. 5. Some other terminologies like packet,source IP, destination IP , SNAT etc was also discussed. Thank you sir.

in todays session we learned about bare metal and virtualization Public ip and private ip SNAT and DNAT and much more

Docker architecture explanation,concepts of base metal architecture, hardware virtualization and finally docker virtualization technique, why docker is fast,networking concepts,networking with docker continued

In this I have learnt about Drawbacks of virtualization Docker engines Docker drivers SNAT, DNAT,PAT Commands of docker

Learned about Docker architecture About docker engine SNAT and DNAT

2020.05.01.03 Learned about Architecture of docker to see why it works fast.... Also why virtualization is better than bare metal.... Cmnds.... Pstree, rpm -q kernel etc... Snat and dnat, pat Ip tables Host driver

In this session we learned about kernel and its importances. Architechture of a virtualisation also how to use for containers.Multiple answers of why containers are fast. Ram and Kernel can be shared with multiple operating system. We also see what is NATing,DNATing,PATing, etc. How to make the Docker available for a whole network using some driver/PATing/Overlay.

* We need an os for the interaction of hardware and software and we can run programs with the help of os. * Kernel scan all the hardwares and load the drivers when we launch an os. * Hypervisor: The software that allocates the machine resources to multiple os as per the user to provide complete utilization of those resources and this concept is known as virtualization. * Limitations of virtualization: we have to install kernel and load all the drivers everytime we launch os which is a wastage of resources. Containerization resolves the drawbacks of bare metal and virtualization. In containerization we have only applications inside the os and it shares the kernel, driver and other resources from the base os. The program on which this setup works is known as container engine. * unake -r command (command to show on which kernel the os is running). * Parent process is the first process to run when the kernel starts and it's PID is always equals to 1 (In rhel parent process is systemd). * pstree command * About packet, source IP and destination IP * SNAT (source network address transmission)- replacing source IP which router's public IP * DNAT (destination network address transmission)- replacing public IP with router's IP. * PAT (port address transmission) * Concept of host network driver

We learnt about Docker architecture Docker engine Bare metal Virtualisation Kernel Public and private ip SNAT and DNAT PNAT Host Network

Rise 2020.10.11.4 In this session,I was learn about the Learn core concepts Artiticture of docker

i learned about: 1 docker engine 2 docker architecture 3 SNAT & DNAT 4 public & private ip 5 bare metal & birtualisation

In this session I am able to learn about the docker architecture as well as about the docker engine. I'm also able to learn about the public ip and private ip. About virtualization as well as contarization.

In this session we go through: > Bare metal setup is when we install OS on the top of hardware > Hypervisor and Virtualization > uname -r command to know the kernel > Conatinerization and container engine > we dont have to install kernel in the container it is sharing the kernel of base OS > it aslo share the RAM of the base OS, also share many library > here we see why docker is fast > pstree command show the process running in the form of tree here we can see in Rhel 7/8 the first process run is the systemd > systemctl command work inside the systemd command > IP are of two type private and public and public on connect to public and private only connect to private IP > Source Network Address Translation (NAT) changes the IP of the packet so that when it goes to ISP then it doesnt spot it over here because it doesnt allow the private IP > SNAT and DNAT > In DNAT there is some disadvantage as if we have more containers, to overcome this we use PAT (Port Address Translation) > to enable PATing simply just add -p 1234:80 that is port no of the router to the port no of the container > for that we have to start firewall also but it work on Rhel 7 > host network > Using Overlay we have to use cluster tech Thats all Thankyou

RISE 2020.62.2.2 yesterday session... - architecture of containers - architecture used for containers - why containers are fast.. Diff reasons.. - kernel is the one of the heaviest and most important part in os.. - kernel and ram can be shared with in the OS's.. - NATing - PATing - DNATing - SNATing - making my container available to whole my network using host driver Or PATing and Overlay..

in this session, I learned the limitations in the bare metal method and why it got shifted to the virtualization concept. I understood what is hypervisor technology which is nothing but virtualization and what are the limitations in this concept.I understood what is container engine and how it helps in sharing resources like RAM, CPU and kernel, and drivers.I understood why systemctl does not work in docker as the systemd process does not start in the container as it shares the kernel and drivers from base os and that was one of the reasons why docker is so fast in launching the OS.i understood what is SNAT and DNAT and how it helps in connecting from private IP to public IP.i understood what is PAT that is port address translation and how it helps to connect from public IP to private ip.i understood what is host driver and its use case like it creates the container that has the same IP as the base os so that I can connect from public IP to private IP even if it is in private LAN.

Discussion about docker architecture. Docker engine Public IP and private ip. Snat and dnat Virtualization and bare metal concepts were also discussed. Commands such pstree, systrmctl and reason not working, host type network were discussed. RISE 2020.10.3.5

RISE 2020.41.7.1 RISE 2020.50.2.1 From the session I have learnt about 1) SNAT &DNAT 2) Hypervisor 3) virtualization 4) docker engine

ID- RISE.2020.25.7.2 In today's session we learnt about docker architecture,docker engine,NAT,SNAT,PAT etc,bare metal and virtualization,public and private ip and why docker is so fast.

Do you have other videos of vimal sir ?? If yes please upload

summary of this session: the architecture behind the docker >>why service command doesn't work in docker container >>something about Nat and Pat and network flow >>advantage of containerization >>configuring firewalls >>IP tables thank you vimal sir Rise ID: 2020.8.24.1

In this session i have learnt drawbacks of base metals can be resolved by virtualisation and drawbacks of virtualisation can be resolved by docker. docker architecture docker engine pstree command hypervisor pat port adress translation use dnat snat systemd command.

RISE 2020.75.8.4 Learned about docker architecture About docker image Ips types

In today's session I learnt Barematel and virtualization DNAT and SNAT Docker architecture and engine Process tree Public and private ip Memory wastage

RISE 2020.79.1.1 In the session, I learnt about docker architecture Public and private IP About bare metal Docker engine Virtualization Networking concept like SNAT and DNAT Docker port mapping