Scribd
Upload
36 views8 pages

Session - 23: Continuous Delivery & Devops

This document discusses key concepts related to Continuous Delivery and DevOps including Dockerfile builds, Docker Compose, Docker Registry/Hub, and Docker networking. It provides details on using Dockerfile to build custom Docker images, how Docker Compose is used to define and run complex applications, how Docker Registry helps share Docker images publicly or privately, and the different types of Docker networks including bridge, host, container, and none modes.

Uploaded by

Sasidhar chowdary
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
36 views8 pages

Session - 23: Continuous Delivery & Devops

This document discusses key concepts related to Continuous Delivery and DevOps including Dockerfile builds, Docker Compose, Docker Registry/Hub, and Docker networking. It provides details on using Dockerfile to build custom Docker images, how Docker Compose is used to define and run complex applications, how Docker Registry helps share Docker images publicly or privately, and the different types of Docker networks including bridge, host, container, and none modes.

Uploaded by

Sasidhar chowdary
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Session – 23

Continuous Delivery & DevOps


Key Points:

• Docker file Build


• Docker Compose
• Docker Registry/Hub
• Docker Networking

2
Dockerfile Build
• Dockerfile is used to create custom Docker image using
Docker build command
• Docker build command follows syntax below
docker build -t <image_name >:<tag>

• This command creates an intermediate container, and that


container will automatically be removed once image build is
complete
Docker Compose
• Docker Compose is used to
define and run complex
applications in Docker
• The main functions of Docker
Compose are building images,
scaling containers, and rerunning
containers that have stopped
• It has a similar set of commands
like Docker
• Entire configuration can be
stored and versioned along with
the project
Docker Registry/Hub
• Docker Registry helps you share Docker images.
• You can also have different collaborators to a single Docker
image.
• Both public and private both Docker images can be uploaded to
Docker hub.
• Docker store consists of enterprise and trusted Docker images.
• You can upload various versions of the same Docker image
• The free account of Docker hub supports unlimited public Docker
images and only one private Docker image
• Some of the private Docker Registries, other than Docker hub
and Docker store, are listed as below
Google Container Registry, Amazon ECR, Jfrog Artifactory,
Nexus Artifactory
Docker Hub Configuration
Docker Registry/Hub
• Docker login command is used
to connect to Dockerhub from
Dockerclient CLI. Before this
can be done, you must tag
existing image with Docker
image concatenated with
Docker username.
dockertag
<image_name><tag>
<docker_hub_username>/
<image_name><tag>
dockerpush
<docker_hub_username>/
<image_name><tag>
Docker Networking
• Docker Networking helps Docker container to interact with other
microservices over the network. Access to multiple applications
hosted inside the Docker container is possible through Docker
Networking
• There are four types of Docker networks
• Bridge Mode It is the default network available for Docker containers It helps
to access Docker container using same Docker host IP address and port.
• Host Mode This will inherit all network resources directly from host and can
become exposed directly to public network This is faster than Bridge mode,
but there might be some security issues
• Container Mode This mode helps to have a unique IP address for each Docker
container You can not access the application through external server, but you
can access it using Docker container IP through internal server
• None in this mode, networking gets switched off and Docker containers could
not be able to connect to the network anymore This helps to setup the
applications network is not needed

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy