github/container.training
1
0
Fork 0
mirror of https://github.com/jpetazzo/container.training.git synced 2026-07-28 01:01:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

remove deprecated rkt, mention runtimes are different per distro

Browse Source
This commit is contained in:
Bret Fisher
2019-11-08 00:19:35 -05:00
parent bc885f3dca
commit 5749348883
2 changed files with 2 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
slides/containers/Container_Engines.md
View File

@@ -104,22 +104,6 @@ like Windows, macOS, Solaris, FreeBSD ...
---
## rkt
* Compares to `runc`.
* No daemon or API.
* Strong emphasis on security (through privilege separation).
* Networking has to be set up separately (e.g. through CNI plugins).
* Partial image management (pull, but no push).
(Image build is handled by separate tools.)
---
## CRI-O
* Designed to be used with Kubernetes as a simple, basic runtime.

4
slides/k8s/concepts-k8s.md
View File

@@ -191,12 +191,12 @@ No!
- By default, Kubernetes uses the Docker Engine to run containers
- We could also use `rkt` ("Rocket") from CoreOS
- Or leverage other pluggable runtimes through the *Container Runtime Interface*
(like CRI-O, or containerd)
- Different install methods and distributions use different runtimes
---
class: extra-details