Introduction to DOCKER Container

Summary

Highlights

• Docker originated in March 2013 and revolutionizes containerized application deployment 🚀.
• The 'Develop, Ship, Run Anywhere' motto captures Docker's essence of enhancing portability 🌐.
• Containers provide a solution to infrastructure challenges, allowing applications to move seamlessly across environments 🌟.
• Docker containers are lightweight, making them scalable and efficient for versatile applications 🏗️.
• Cloud computing platforms serve as excellent hosts for Docker containers, unifying technology usage ☁️.

Key Takeaways

• Docker containers enhance portability and scalability in software deployment 🌍.
• Containers help bundle applications with their dependencies for consistent performance 💼.
• Docker is lightweight, benefiting quick deployment and resource efficiency ⚡.
• Cloud platforms can efficiently host Docker containers, enhancing capabilities 🌩️.
• Docker eliminates the "work on my machine" problem, easing collaboration 🤝.

Overview

Chapters

• 00:00 - 00:30: Introduction to Cloud Computing The chapter titled 'Introduction to Cloud Computing' discusses the evolution of cloud computing. It highlights the advantages and benefits that have emerged as the technology has developed.
• 00:30 - 01:00: Cloud Computing Challenges and Associated Technologies The chapter discusses various challenges in cloud computing and the technologies associated with addressing these challenges. It explores the core architecture of cloud computing and examines different technological advancements that have emerged in conjunction with it. The discussion highlights that while these technologies may not be entirely new innovations, they represent a collective approach to harnessing existing innovations and approaches into new developments.
• 01:00 - 01:30: Introduction to Container Technology The chapter introduces container technology, highlighting its significance in addressing the challenges associated with infrastructure, platform, and software development. It suggests a transition from traditional in-house installations to more modern solutions, without yet delving into specific technologies or methods.
• 01:30 - 02:00: Container Portability and Application Diversity This chapter discusses the challenges of software deployment in modern service infrastructure environments. It emphasizes the role of different service types such as Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). A key issue addressed is the need for redeployment, reconfiguration, or recompilation of software packages when transitioning between different environments, highlighting the growing complexity in software development and deployment.
• 02:00 - 02:30: Motivation and Development of Container Technology The chapter discusses the major motivation behind the development of container technology, focusing on the advancement of resourceful devices such as mobile phones, laptops, notepads, and smartwatches. These devices are capable of running various applications, highlighting the need for efficient technology to manage and optimize resources across diverse platforms. By leveraging these advancements, container technology aims to provide a streamlined solution for application deployment and management, ensuring optimal performance and resource utilization.
• 02:30 - 03:30: Shipping Analogy for Containers In this chapter titled 'Shipping Analogy for Containers', the concept of application portability is discussed. The text highlights the challenge of transferring applications across different environments and introduces container technology as a solution. Containers allow bundling of applications along with their dependencies, facilitating easier and more efficient portability across varied environments.
• 03:30 - 04:00: Introduction to Docker Container The chapter introduces Docker Containers and discusses their relevance in modern computing. It begins by explaining how containers can be deployed in different environments, which is crucial for applications to function. The chapter indicates that cloud platforms often host these containers, although there are opinions suggesting that container technology is somehow opposed to cloud computing. Nonetheless, current trends reveal that containers and cloud platforms are not adversaries, highlighting their compatibility and mutual benefits in deploying applications.
• 04:00 - 05:00: Features of Docker The chapter discusses the role of cloud platforms in hosting containers and enhancing their capabilities by adopting container technology. A specific focus is given to Docker, an open-source container that has gained significant popularity. The chapter promises to provide a brief introduction to Docker.
• 05:00 - 08:00: Docker Components and Variants This chapter introduces Docker, focusing on its role in achieving software portability and its connection to cloud computing. Docker was initially released in March 2013, and the discussion highlights how container technology facilitates deploying applications across different computing environments.
• 08:00 - 10:00: Traditional Virtualization vs Docker Architecture Chapter Title: Traditional Virtualization vs Docker Architecture Summary: This chapter introduces Docker as a container management service, emphasizing its core philosophy of 'develop, ship, and run anywhere.' The approach ensures that applications developed using Docker can run in any environment, including desktops and Android devices, thus providing flexibility and portability across different systems.
• 10:00 - 11:30: Concepts - Images and Containers The chapter discusses the concept of containers in computing and how they are utilized across various environments such as iOS, cloud platforms like OpenStack, Azure, IBM Bluemix, and Amazon Web Services. It highlights the role of Docker in helping developers easily create applications and package them into containers for deployment across these diverse environments. The primary aim of Docker is to streamline the application development and deployment process.
• 11:30 - 13:30: Containers vs Virtual Machines The chapter discusses the current popularity of using containers in modern software development, especially in agile projects. It highlights that containers have become somewhat of a buzzword in the industry. The chapter aims to make an analogy to clarify the distinctions and utility of containers compared to virtual machines, looking at the evolution of computing paradigms.
• 13:30 - 15:00: Docker Ecosystem and Cloud Integration The chapter "Docker Ecosystem and Cloud Integration" explores the diverse hardware environments where Docker can be effectively utilized. Examples include laptops, desktops, specialized boards, and chassis with blade servers, as well as network devices. The discussion focuses on the capability to build and transfer applications across these varied platforms, emphasizing the flexibility and adaptability of Docker in integrating with different hardware and the cloud environment.
• 15:00 - 16:00: Application Level Virtualization and Docker Terminologies The chapter explores the challenges faced in application deployment, particularly focusing on the need for recompilation and redevelopment when transitioning applications between different server environments. This process requires significant manual effort and manpower, as highlighted in the discussion. Furthermore, the chapter introduces concepts related to application level virtualization and Docker, which can potentially alleviate some of these issues by facilitating smoother application deployment across diverse systems.
• 16:00 - 20:30: Docker File and Docker Hub This chapter discusses the evolving landscape of technology where new systems and software are regularly introduced. It highlights the diversity in applications ranging from static websites to complex systems involving databases, analytics, and API endpoints.
• 20:30 - 22:00: Conclusion and Docker's Applicability The chapter discusses the rapid development occurring in web front-end technologies and the complexity involved in transferring applications between different environments. The focus is on the challenges of recompilation and reconfiguration, highlighting the difficulties associated with achieving interoperability.

Introduction to DOCKER Container Transcription

• 00:00 - 00:30 hello so welcome to the ah course on cloud computing ah so so far what we are discussing is about that how this cloud computing evolved what are the different ah advantages and ah
• 00:30 - 01:00 challenges in cloud computing what are the different associated technology to this cloud computing ah aspects so core architecture and what are the different other type of technologies which came up with those things so as we have seen it ah may not be a totally ah new technology or new invocations as such but it is trying to look at all these invocations all these ah new ah approaches and coming up the things another ah as another ah new development what
• 01:00 - 01:30 we will look today is a ah container technology right so what we are ah finding ah one way as as we have seen that ah there are challenges in infrastructure build up there are challenges in platform build up there are challenges in software build up thats why we try to migrate from our in house ah installation to some
• 01:30 - 02:00 service providers installation so typically as we have discussed on xas type of services infra structure ah platform and software these are the different type of services another another problem which is coming up ah nowadays is ah or rather ah with the development of ah software and ah other developments like there is a re deployment or reconfiguration or recompilation of the software whenever we want to ship one package from one environment
• 02:00 - 02:30 to other this is ah the one of the major ah motivation towards these these stays we are having devices which are ah pretty resource full say your mobile say your mobile device or ah some notepad or laptop or even these days ah smart watches so all those things are resource full and able to run different applications right so one way is a looking at that sort of things
• 02:30 - 03:00 other way another ah aspects of it is ah we are having variety of applications development across the things right so this type of portability of one application from one environment to another is becoming a major challenge so there there were the container technology came into picture where we will be able to ah bundled up the application along with these associated ah dependencies into a container
• 03:00 - 03:30 and ah push it as a single container to the other type of environment i mean the amount container fits your applications start to start working on that so cloud ah in such cases can be a platform to host this container though there are some of the some in some literature or in some forum people say this container technologies is something a contended to the cloud but what we see these days not exactly a ah a container to or a something
• 03:30 - 04:00 which is ah which is fighting with cloud rather we can cloud can act as a platform to host these container and basically cloud can enhance its capability by ah adapting this ah container technology right once such container which is which has become a very popular is the docker a open source container which has become a ah docker so what will see we will see a brief introduction
• 04:00 - 04:30 to this docker container right it is ah it will help us in understanding this how how this portability of ah different systems and software will be there and also help us in looking at this container technology with with a with a background of a cloud computing so if you look at ah that docker it is somewhere initial release where march twenty thirteen
• 04:30 - 05:00 so its a container management service right main feature of docker are develop ship run anywhere so this is this key words if we can see like develop ship it and run anywhere so you irrespective of where it is it should be able to run this is basic philosophy of docker which tells everything like you develop once and ah ship to any environment and run to this it can be a it can be any your desktop environment it can be a ah android environment
• 05:00 - 05:30 it can be a ios environment it can be a say ah any cloud environment it can be open stack it can be azure it can be ah blue mix or amazon anything right so that thats exactly the container things trying to say so the docker aims at facilitating developer to easily develop applications ship them into containers which can then be deployed
• 05:30 - 06:00 anywhere right it has become the buzz word of for modern world development especially in the face of agile based projects right so this is this is the ah buzzword this days is ah to look at the this type of things we will try to make a quick analogy of the things and try to understand what is what is there in this type of things now if you look at ah how our computing paradigm develop so it was somewhere a system like
• 06:00 - 06:30 it may be a somewhere something like a laptop or even desktop or some ah specialized board or a chassis with blade servers and any type of things even even if i can look at some devices like network devices where we basically build some applications ah for them right now if i am running something on on a particular laptop and then put it to want to put it to
• 06:30 - 07:00 want to run it on a server thing then in some cases ah in in most of the cases i need to recompile the things right i need to align the things or redevelop not that ah redevelop the whole thing but i need to re develop a ah major portion of the things or recompile the of the server i want to do for another type of in first ah i in another type of ah system i need to again redevelop the things so what what is happening that there is a lot of ah man power uses into the things whereas
• 07:00 - 07:30 on the other side so so one side that there is a large day miss or there is a everyday we are coming or means ah periodically you were coming with new systems and softwares and ah and ways and type of things on on the other hand we have several applications which are coming up on the other hand some may be static static website something like background worker like python ah and so and so forth user db analytics db queue ah api endpoints
• 07:30 - 08:00 web front point end and endless things are being developed right now if you look at that for everything if you want to have if you want to sip a application from one to another and if we want to this sort of ah recompilation or ah reconfiguring the things its a hell of a job right so ah so what we try we when look at that interoperability
• 08:00 - 08:30 or portability what we try to do we try to set up a matrix like say static website whether it will run on this ah particular device whether you run on this device and so and so forth right ah its a user db and type of things right so if i ah put tick on this matrix then this is there so our major objective is there with minimal ah investment in terms of man power skill infrastructure and ah software and so
• 08:30 - 09:00 and so forth i should be able to have all ticks on this matrix like anything can run anywhere type of situations right so thats a thats a big challenge this a this a big challenge to add here but never the less the whole computing world wants to achieve this right this is these leads to commercialization of a product in a better way marketability of a product in a better way and ah rather in some cases like if you look at sensor based
• 09:00 - 09:30 technologies if the if the sensor applications runs only on a particular type of smart phone and or a particular type of os and it is not running to the other things then your capability also decreases right i could have captured through different type of mobile devices ah but that portability becomes a major challenge so these are these are some of the things which are which has driven that i whether i can have a somewhere some intermediate mechanisms
• 09:30 - 10:00 which allows me to transfer this data now if we try to look at some analogies look at shipping i want to sip some product form one to another so ah one side this products are there like there is there can be variety of products like it can be a box it can be a car it can be a some barrel it can be even a piano and ah drums and servers and etcetera so these are the things i want to ship from
• 10:00 - 10:30 place a to b and it can be shift in varies form it can be in somewhere some ah trucks and sort of things somewhere can be dumbed in to a racks some fork lifter to lift on the things somewhere some locomotive or trains being manufactured out of factory and see it and through crane and put on the ship for shipping from across the continent right so there are a variety of products and variety of ah techniques and technologies which are
• 10:30 - 11:00 involved in shipping this products right unless i standardize like the if you thing that the type of ah mechanisms require for a server we will differ in differ from how you do for a piano or what you do for a car right so unless i make a standardized way of doing this approach doing ah this business then things will not work right so what they found out ah they found out a concept for this sort of a docking station or this sort of a chamber
• 11:00 - 11:30 where if it fits in it can be shipped so what a what we do we a any product we put into a this sort of docking station right or this type of a box and that this box has a standardized size standardized mechanism of holding and it can be either put on rack put on fork lifter
• 11:30 - 12:00 put on crane put on ship can be taken out from factory or inside the factory or put on the trucks and carry it then these are very popular now ah i made this shipping thing to any type of the any type of ah mechanism to transport by making a intermediate mechanism call shipping containers right whether i can make ah this thing feasible for our ah applications for our ah software applications now this container
• 12:00 - 12:30 is a standardized size right so if the if you can if somebody can hold the container it can hold this products right so what it what it does the inside the container is more on the product which dictates outside the container the infrastructure which dictates right this outside the ah environment of the container is more inclined towards this infrastructure
• 12:30 - 13:00 by which it is shipped or where it is stored and type of things inside the container is is the way where the product is stored right like ah like like piano may have a different requirement of environment than ah car than a server systems right so this this same type of conceptually the same type of philosophy is being carried
• 13:00 - 13:30 to these ah ah this when we talk about container ah platform when we talk about docker right so same thing what we say its a docker service we have different ah applications and there are different devices and if i can dock it in somewhere other right which is standardized and if these devices are able to handle this container or docker container then my application
• 13:30 - 14:00 will run so what inside that container is there based on the applications all these related libraries binaries dependences etcetera are contained in this thing externally where which infrastructure it is running that is important right so so this sort of philosophy ah helped in ah as we a staring that you develop and sip to anywhere right develop build sip anywhere right so
• 14:00 - 14:30 it is if this type of technology is becoming extremely popular ah and becoming a defect standard ah for this and what what we feel that is necessary to discuss because most of the cases what what we are doing in a cloud we are trying to run different applications ah with in this cloud right like if you look at say i i want to run in a particular banking
• 14:30 - 15:00 application or we talk a talk about some special ah web service applications so what it what it tries to do it tries to build up ah build a ah a container particular container class in a sense or a club of services which need to be shipped or needs to be run at different ah different environment let it be ah let it be ah as your cloud let it be open stack
• 15:00 - 15:30 cloud let it be ah any other sort of cloud like ibm blue mix or amazon or google cloud platform any type of platform i my basic requirement is there i should not develop redevelop for every environment right and as well it should run if if the resource permits on my smart phone or my desktops as systems or server and so and so forth
• 15:30 - 16:00 so this sort of portability of the things this container brings into ah picture so if we look at again that the basic features so docker has the ability to reduce the size of development by providing a smaller footprint of the operating system by a containers right so in the container you have a smaller footprint of the os with containers it becomes easier
• 16:00 - 16:30 for software teams such as development qa teams operations to work seamlessly across different ah across applications right so they are may be a different centers even for a one organizations and it can work seamlessly because finally it should fit into the container in being shipped to the other things right one can deploy docker containers anywhere on any physical and virtual machines and even on cloud right so it is a docker containers ah can be deployed anywhere practically anywhere
• 16:30 - 17:00 or any physical or virtual machines in vms are physical servers and even on cloud since docker containers are pretty lightweight they are easily scalable right that is an important factor so this container this docker container is light weight and as it is light weight then scalable scalability is much easier if there is a heavy heavy weight stuff then there
• 17:00 - 17:30 is resource requirement will be much higher and anything portability is becomes or scalability or scaling up or especially scaling up becomes extremely difficult so as this is light wright this is much easier there are different ah variants or what we say different ah flavors of things or components so docker for mac it allows one to run docker container on mac os docker on linux it allows
• 17:30 - 18:00 one to run docker container on linux os docker for windows docker docker engine right it is used for building docker images and creating docker containers ah some sort of ah a over the bare metal os you have the docker engine over this docker containers are placed like some some sort of analogy with the hypervisors of a particular virtualization system docker hub this is a registry the important ah thing registry which is use to host various
• 18:00 - 18:30 docker images right so this docker hubs hub you will find various docker images if you are a developer you can basically um submit in the docker hub which can be used by others to use it docker compose this is used to define application using multiple docker containers right so its a composition sort of composition service which which is ah used to define applications using multiple docker container so these are different components there are various others
• 18:30 - 19:00 or there ah different flavors of these docker or different components of this docker so if we look at the traditional ah virtualization so ah we have that ah underlining server or bare metal or the backbone systems physical systems over that there is a host ways which basically provide this service to this server over that we have that hypervisor right or
• 19:00 - 19:30 vmm or virtual machine monitor and this helps us in generating different vms right and ah every vms can have their own guest os and over the guest os different applications runs so this is the basic philosophy of virtualization already we have seen so the server is the physical server that is used to host multiple virtual machine host os is the base machine
• 19:30 - 20:00 such as linux or windows hypervisor as either some sort of hypervisor it can be vm ware xen ah kvm and type of things or ah commercially vmware or widows hyper v that is used to host virtual machines once should then install multiple operating system as virtual ah as virtual machines on the top of the existing hypervisor as guest os so what we do so in case of a ah iaas type of cloud and then host your application on the top of each guest
• 20:00 - 20:30 os so this is this the way normally a traditional virtualization work a variant of this ah docker architecture is that it has the server os case two s and then we have the docker engine so over the docker engine we can run different apps right so it is it is it is ah it is going to be light weight and of course you may not do very large applications but never the less if your application is not so demanding you can basically deploy
• 20:30 - 21:00 out here server is a physical server that is used [hoss/host] host multiple virtual machines host os is the base machine such as linux or windows docker engine is used to run operating systems which is earlier used to be virtual machines at docker containers right so it is running ah ah operating systems which is earlier used
• 21:00 - 21:30 as a virtual machines as docker containers and then finally all apps now run on the docker containers right so it is it has now docker containers where this different apps run on this docker container so what we see there is a though the philosophically may be ah same that ah same sort of aspects is there but the it is there is some difference with this traditional virtualization
• 21:30 - 22:00 so just to recap that containers ah are abstraction at the app layer that packages code and dependencies together right so its a what is this container including docker container its an abstraction at the app layer that application layer that packages or bundle code and dependency together so it is it is together bundled multiple container can run on the same machine and share the
• 22:00 - 22:30 os kernel and other containers each running on isolated processes in the user space right so that is also possible container takes up less place then virtual machines container images typically tens of mbs in size and start almost ah instantaneous as that is exactly what we were discussing it is a low weight and ah we can ah much less ah resource hungry than virtual machines and
• 22:30 - 23:00 it can start instantaneous it is as it is a low weight so there are other ah few concepts which are ah which are comes back to back one is that image so ah we are talking about images and type of things so in a an image in this context is a light weight standalone executable package that includes everything needed to run a piece of software including code runtime libraries environment variables config files etcetera simply important right
• 23:00 - 23:30 so it is a it is a light weight standalone executable package that includes everything needed to run that particular software package or software ah software including code runtime libraries environment ah variables configuration files everything a container is a runtime instance of an image that the ah what the image becomes in memory when actually is executed
• 23:30 - 24:00 right so what you what is there so i have a bundle things once it start running ah it is a instantiation of this image that is exactly the container it runs completely isolated from host environment by default only accessing the host file and ports if considered to do so right so it is ah ah it is independent of the host environment so other things there container runs apps natively on the host machines kernel right
• 24:00 - 24:30 they have better performance characteristics than virtual machine that only get virtual access to the host resources through a hypervisor so it it runs directly on the host machines kernel containers can get native access each one running in a discrete process taking no more memory then the then any executable so it is it is not only light weight it is ah it has performance wise also instantaneous so if you look at containers and virtual machines
• 24:30 - 25:00 so if ah means if we look at repeat that things we have the underlining re infrastructure of the server base host base docker and then we have that container right it has the applications with ah other dependencies right where as ah in case of a hypervisor or a virtual machine over the hypervisor we have guest os and rest of the things right
• 25:00 - 25:30 so thats the ah difference so virtual machine run guest operating system os layer in each box resource ah intensive so as it is ah requires more resources resulting disc image and obligation state in a ah entangle with the os settings right ah system installed dependencies where security paths and so and so forth whereas container can share a single kernel and only
• 25:30 - 26:00 information that needs to be in a container image is the executable and its package dependence right so what are the different other package dependencies which never need to be installed on the host os because it is bundled together these processes run like native processes and can be managed individual every container because they contain their dependency there is no configuration entanglement and so containerized applications runs anywhere (Refer Time:26:00) so that means
• 26:00 - 26:30 i i dont have any ah so to say any binding with this host machine right so that means i i i isolate the this my container based package with the host so i it is ah it go it increases the portability and can be run any other ah system so same thing so if we if there is a running on a vm then we have ah every app ah every copy of an app every
• 26:30 - 27:00 slide modification requires a some new virtualize environment whereas in this case ah slight modification ah can be done allows us only to save the difference between container a and container a dash and that can be done at the ah at at that container level so ah overall working as we as we have the docker ah as we have seen this is the docker
• 27:00 - 27:30 engine is there so form the source repository build over this docker engine its a container a particular container ah class container a a put it push it to this container image registry which is ah which can be search search by the users or the consumer this container ah finally is basically ah this docker is a some sort of a client server mode operation
• 27:30 - 28:00 so it search and then pull this things and run on the on this particular ah different instantiation of the different container classes so ah of we try to look at all together like how it can run on the cloud so i we have infrastructure hypervisor over that guest os we can have a docker services right in this case we have due to different container here only one and so and so forth so the cloud ah can host or
• 28:00 - 28:30 can can become a platform ah for running this ah container type of services so that is on some vms that is in a iaas type of cloud we can run this sort of services so there are ah needs are ah enormous or needs requirement applicability ah is enormous like
• 28:30 - 29:00 ah application level virtualization ah is possible a single host can run several special application for utilization of resources as we have seen when we discussed about special cloud there are several special applications and now we can have a single host which can run several special applications build ones deploy anywhere run anywhere type of things ah philosophy so i once i develop and build it and then i deploy anywhere run anywhere
• 29:00 - 29:30 better collaboration between development ah development of web of applications so i can have better collaborative applications into the ah thing into into place there are few terminologies ah some of them already have seen so like images list of all local images ah run create a container from an image and execute a ah command in it tag
• 29:30 - 30:00 an image pull download an image from a repository rmi delete a local image so this is also remove intermediate images if no no longer is used so that ah resources can be release there are some terminology which are more ah what we more associated with docker container like ah ps list all running containers ps minus a list all containers ah including the stopped
• 30:00 - 30:30 one top display process in the container start stop pause rm delate a container commit create an image on the container what you may notice that these are the most of the many of them things are some sort of linux commands right already we are used to it so in this case is also for container we can use those ah commands ah those were interested you can
• 30:30 - 31:00 ah basically hook into docker dot com and see that how the coding can be done and how they a container can be build using a ah docker engine so this is freely downloadable and you can work and you can run that things on ah your ah desktop or server or even on your android devices ah make a make a particular application and and run on different devices so there are some few more things one is the docker file create an image automatically
• 31:00 - 31:30 using a build script called docker file can be versioned in a version control system like git or svn along with other dependency docker hub can automatically build images based on docker files on github right so this is this this are things are possible and ah the docker how where the public repository your docker images are there like hub dot docker dot com there is a good resource full area for this docker ah images ah and automated has been
• 31:30 - 32:00 automatically build on docker file source for build is available on the github so finally if we look at that different view point or different uses of these docker is a worldwide ah claim to be leading software container platform ah being used ah at ah various levels various ah at at in different environment and became very popular so develops
• 32:00 - 32:30 a purse use docker to eliminate work on my machine problem right so that is dependency on the things when collaboration on code and coworkers ah collaboration on code with coworkers are much needed operators use docker to one ah and manage apps side by side in isolated container to get better compute density that is the view point or the usage of the operators
• 32:30 - 33:00 enterprise usage docker to build agile software delivery pipelines to ship new features faster more securely with confident for both linux windows servers linux on mainframe apps and so and so forth right so there are different applicability of the docker and this ah this services services becoming ah pretty popular and those who are ah interested ah in this ah particular um
• 33:00 - 33:30 docker technology ah you may go through that docker dot com and there are several other open sources where you can see that how this compilation can be done and and can have your own ah docker images and run out on different platform as see the things right so as per as the cloud computing paradigm is concerned it acts as a platform and have seen application
• 33:30 - 34:00 portability across cloud making cloud more ah useful more acceptable at different environment thank you