Docker
@rkstlohchab
intro
To understand the docker, we need
to understand the problem statement
that the docker is trying to resolve.
When developers create something,
it may work smoothly on their own
computers but encounter issues
elsewhere (servers etc).
@rkstlohchab
Docker solves this by packaging the
project in a way that ensures
consistent performance across
different environments.
This resolves common problems such
as image loading failures or file path
discrepancies, ensuring a professional
and seamless experience.
@rkstlohchab
containers
Docker provides airtight containers
that are central to its functionality.
These containers package your entire
codebase and are very portable,
which is one of Docker's main
benefits.
@rkstlohchab
containers
You can take these containers and run
them anywhere, and they will work
just like they did on your machine.
Additionally, Docker allows for easy
sharing and collaboration with its
social containers feature.
@rkstlohchab
containers
These containers include your code,
dependencies, configuration, running
processes, and networking
information.
In special cases, they also contain
parts of the operating system that
tweak your code.
@rkstlohchab
images
Docker images are lightweight,
standalone, executable packages that
contain everything needed to run a
piece of software, including the code,
runtime, libraries, tools, and settings.
Images are created from a Dockerfile,
which specifies the instructions
needed to assemble the image.
@rkstlohchab
images
They serve as the basis for Docker
containers.
These images can then be stored in
repositories and shared with others,
making it easy to distribute and
deploy software across different
environments.
@rkstlohchab
volumes
There is a problem: a container is a
removable item, so whenever the
container is destroyed, so is data.
Volumes in Docker help to store data
persistently. They reserve some
space on the disk so that data from
the database can be stored.
@rkstlohchab
volumes
When we create a volume, it ensures
that the data will remain intact
regardless of whether the container is
running or not. This means that the
data will always be available.
Also, if you have multiple services or
applications that need access to the
same data, you can use the same
volume for all of them.
@rkstlohchab
found it useful?
Follow for more
www.linkedin.com/in/rkstlohchab
@rkstlohchab