Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
9 views4 pages

Class 1

The document introduces containers, highlighting their advantages over traditional server provisioning methods, such as the ability to run multiple software applications within a single operating system while isolating their environments. It discusses various components of container architecture, including container hosts, clients, images, and registries, as well as tools like Docker and Podman. Additionally, it touches on concepts like namespaces, cgroups, and orchestration tools like Kubernetes.

Uploaded by

Resham Saharan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
9 views4 pages

Class 1

The document introduces containers, highlighting their advantages over traditional server provisioning methods, such as the ability to run multiple software applications within a single operating system while isolating their environments. It discusses various components of container architecture, including container hosts, clients, images, and registries, as well as tools like Docker and Podman. Additionally, it touches on concepts like namespaces, cgroups, and orchestration tools like Kubernetes.

Uploaded by

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

Chapter-1: Container Introduction

Server provisioning team ?

Method ?

1) physical Servers
2) Virtualization: hardware based virtualization

diff

Proble-1: multiple software not able run the OS due some conflict.

Confict (LIBS)

1. ManPower
2. Delay ?
3. Cost ?
RHEL:

1. License
2. Memory/CPU/storage

Container:

Docker Training Page 1


1. We can deploy multiple software inside the Single OS.
2. Container it create isolate env between the software
3. It keep separate libs/binary/config file any software

1. Software provisioning time .


2. Software migration
3. Cost
docker images
Podman images
Docker run
Podman
Docker ps
Podman ps

Quiz-1 ? No

Quiz-2: Physical Servers: OS (Containers)

Container Arch ?

1. Container Host : the machine there we are deploying containers .

OS: (Physical/Virtualized ) Linux/window

H/w: 2Gi/1cpu/10HD

Software : docker , Podman , LXC , Rocket ,

docker-ce: community edition


docker-ee: enterprise edition

2. Container Client

3. Container Images: it contains software related depends


it is the small package of software depend.

1. community based:

Docker Training Page 2


1. community based:
2. Custom Images :

4. Container Image Registries : there is server , there we are storing all the images .
1. Public / Community:
1. docker.hub/docker.io
2. registry.access.redhat.com
3. registry.redhat.io
4. gcr.io
5. quay.io

2. Private Registry : In company Infra

5. Namespaces :

6. Containers : its set of namespace


It is running mode of images.

Note: using same image we can launch multiple container.

7. Cgroup : it limit usages of containers.

8. Container Runtime plugin:

1. Dockerd
2. Containerd
3. Cri-o
Container: standAlone

Kubernetes: orchestration tools:

Opensource:

Kubernetes

Openshift

Vmware

Ranchor

Docker Training Page 3


Docker Training Page 4

You might also like