These slides were presented in a joint Meetup with Docker Bangalore and Cloud Native Bangalore As the name indicates these are the slides for people who're getting started with Containers

1. Onboarding into
Containers

2. HELLO!
I am Yeshwanth Reddy
You can find me at @golazynani
imjuststarting@gmail.com
2

3. Agenda
● What is a Container?
● Why Container?
● Benefits
● Security Concerns
● Security Best Practices
● Container Terminology
● Container Image Format
● Container Runtimes
● Why Should I Care?
● Resources
3

4. 1.
What is a
Container?
A container is a standard unit of
software that packages up code and all
its dependencies so the application runs
quickly and reliably regardless of the
computing environment.

5. 5
Containers and virtual machines have similar resource isolation and
allocation benefits, but function differently because containers
virtualize the operating system instead of hardware. Containers are
more portable and efficient.

6. Why Containers?
Also Why Not?

8. 8
Modern
Application
Requirements Modern
Applications
Maintaina
bility
High
Availability
Micro
Services
Automati
on
Fault
Tolerance
Scalability

9. 9
Just to name
a Few
Benefits
Portable
DevOps Isolation
Faster
Startups
Resource
Utilization
& Costs
Agile

10. 10
Security
Concerns
Be Careful
with
Kernel
Exploits
Compromi
sing
Secrets
Container
Breakouts
DOS
Attacks
Poisoned
Images
Registry?

11. Security Best Practices
❑ Know and control the source and content of the image
❑ Least Privilege
❑ Effective Vulnerability Assessment
❑ Be careful with the Base Image
❑ Access Control
11

13. “Container Terminology is
Deceptive”
13

14. What do You Mean?
- Justin Bieber
Container
Running instance of a
Container Image
Container Image
An lightweight,
standalone, executable
package of software
that includes
everything needed to
run an application
Container Runtime
A software that
executes containers
and manages
container images on a
node
14

15. ● Image Management
● Container Interactions
● Container Lifecycle
CONTAINER RUNTIME
It’s a hub of container images from
where the container images are
downloaded locally and consumed
by the container Runtime
15
CONTAINER REGISTRY

16. LET’S REVIEW SOME CONCEPTS
Container Container Runtime Container Image
16
OCI Container Registry Repository

17. Container RuntimesAfter 3 slides
17

18. Container Image
Format
Container is a Container

19. “With no standard, there
is no way to automate.
Each container is defined
and consumed
differently”
19

20. The mission Open Containers Initiative
(OCI) is to promote a set of common,
minimal, open standards and
specifications around container
technology
20

21. Containerd is an industry-standard
container runtime with an emphasis on
simplicity, robustness and portability
Containerd is one of the most
extensible, well-architected and
optimal runtime focused on simplicity
that is meant to be embedded into a
large ecosystem
CNCF GRADUATED PROJECT
21

22. ● Lightweight container
runtime for Kubernetes
● All the runtime
Kubernetes needs and
nothing more
22

23. A container sandbox
runtime focused on security,
efficiency and ease of use
23

24. 24
A FEW OTHERS

25. Why should I Care?
Container Runtime is a Runtime

26. These parameters differ with
Runtimes
❑ Performance
❑ Stability
❑ Hypervisor Isolation
❑ Security Capabilities
❑ Broad Usage
26

27. “The Benefits of choosing
a Container Runtime is an
Operational Concern”
27

28. OUR PROCESS
IS EASY
28
20XX
CRI
2010
Docker
2015
Open Container
Initiative
2019
We’re Here

29. Resources
❑ https://developers.redhat.com/blog/2018/12/19/security-considerations-for-contai
ner-runtimes/
❑ https://www.ianlewis.org/en/container-runtimes-part-1-introduction-container-r
❑ https://www.oreilly.com/ideas/five-security-concerns-when-using-docker
❑ https://www.redhat.com/en/topics/security/container-security
❑
29

30. Hope I made Sense
Any Questions?

31. 31
THANKS!
GOOO
You can find me at:
❑ @golazynani
❑ imjuststarting@gmail.com