Scribd
Upload
5 views

Docker Intro

Docker allows packaging applications with dependencies into standardized units called containers that can run on any infrastructure. Containers are more lightweight than virtual machines and allow running multiple workloads on a single host. Docker uses a client-server architecture with Docker engines running containers from images and connecting to Docker registries to store and retrieve images.

Uploaded by

Ananth M.
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
5 views

Docker Intro

Docker allows packaging applications with dependencies into standardized units called containers that can run on any infrastructure. Containers are more lightweight than virtual machines and allow running multiple workloads on a single host. Docker uses a client-server architecture with Docker engines running containers from images and connecting to Docker registries to store and retrieve images.

Uploaded by

Ananth M.
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

Docker

BY RAM
Container (Docker)

• Containers are a software package into a


logical box with everything that the
application needs to run. That includes the
operating system, application code, runtime,
system tools, system libraries, and etc. Docker
containers are built off Docker images. Since
images are read-only, Docker adds a read-
write file system over the read-only file system
of the image to create a container.
• Containers are compared with virtual machines
(VMs). VMs are the guest operating system such
as Linux or Windows runs on top of a host
operating system with virtualized access to the
underlying hardware. Containers allow you to
package your application together with libraries
and other dependencies, providing isolated
environments for running your software services.
Docker

• Docker is an open-source platform based on


Linux containers for developing and running
applications inside containers. Docker is used
to deploy many containers simultaneously on
a given host. Containers are very fast and
lightweight because they don’t need the extra
load of a hypervisor as they run directly within
the host machine’s kernel.
Docker vs. VM – where is the difference?
• Docker vs. VM – where is the difference?
• Docker is container based technology and containers are just user
space of the operating system. At the low level, a container is just
a set of processes that are isolated from the rest of the system,
running from a distinct image that provides all files necessary to
support the processes. It is built for running applications. In
Docker, the containers running share the host OS kernel.
• A Virtual Machine, on the other hand, is not based on container
technology. They are made up of user space plus kernel space of
an operating system. Under VMs, server hardware is virtualized.
Each VM has Operating system (OS) & apps. It shares hardware
resource from the host.
• VMs & Docker – each comes with benefits and
demerits. Under a VM environment, each workload
needs a complete OS. But with a container
environment, multiple workloads can run with 1 OS.
The bigger the OS footprint, the more environment
benefits from containers. With this, it brings further
benefits like Reduced IT management resources,
reduced size of snapshots, quicker spinning up
apps, reduced & simplified security updates, less
code to transfer, migrate and upload workloads.
Docker Architecture and Components
five major components in the Docker
architecture:
• Docker Daemon listens to Docker API requests
and manages Docker objects such as images,
containers, networks and volumes.
• Docker Clients: With the help of Docker
Clients, users can interact with Docker. Docker
client provides a command-line interface (CLI)
that allows users to run, and stop application
commands to a Docker daemon.
• Docker Host provides a complete
environment to execute and run applications.
It comprises of the Docker daemon, Images,
Containers, Networks, and Storage.
• Docker Registry stores Docker images. Docker
Hub is a public registry that anyone can use,
and Docker is configured to use images on
Docker Hub by default. You can run your own
registry on it.
• Docker Images are read-only templates that
you build from a set of instructions written in
Dockerfile. Images define both what you want
your packaged application and its
dependencies to look like what processes to
run when it’s launched.
Docker Engine Components
Docker file system -Layers
• Each image consists of a series of layers.
Docker makes use of union file systems to
combine these layers into a single image.
Union file systems allow files and directories
of separate file systems, known as branches,
to be transparently overlaid, forming a single
coherent file system
• Each Docker image references a list of read-
only layers that represent filesystem
differences. Layers are stacked on top of each
other to form a base for a container's root
filesystem. The Docker storage driver is
responsible for stacking these layers and
providing a single unified v

You might also like