High level approach: lightweight VM • own process space • own network interface • can run stuff as root • can have it’s own /sbin/init (different from the host) “Machine Container” #MesosCon
Low level approach: chroot on steroids • can also not have it’s own /sbin/init • container = isolated process(es) • share kernel with the host “Application Container” #MesosCon
Standard format for containers and a place to share them • Fetch an image from the public registry with “docker pull” • Enter an image with “docker run“ and do some changes • Record those changes with “docker commit”, repeat as many times as needed • And then share the result with “docker push” on the public registry, or a private one #MesosCon
Changes in the API 2/2 • Command is now optional so you can use the docker image default one. • Shell boolean added to wrap your command with sh –c “…” to handle symbols like | > & #MesosCon
Small Note Mesos do a docker pull before each run, to make sure you are running the last version. • From the docker index – You need internet access • Local images – You need to run a private registry to host them #MesosCon
vieux
interu
tacck
okazuki
hato3isfriend
oracle4engineer
.png){kind=icon}
pharma_x_tech
ks91
leekwangsoo1995
lamrongol
microcms
techtekt
zakiyama
mthomps
yeseniaperezcruz
ammeep
sachag
addyosmani
iamctodd
holman
thekraken
panda_program
searls
chriscoyier