Dit artikel sil beprate hoe't it wurket
Oer mienskiplike problemen mei Docker en har oplossingen al
Main Features
- Wurkje mei in aparte kearn, dus it leverjen fan netwurk, ûnthâld en I / O-isolaasje, is it mooglik om it gebrûk fan hardware-isolaasje te twingen basearre op virtualisaasje-útwreidingen
- Stipe foar yndustry noarmen ynklusyf OCI (container opmaak), Kubernetes CRI
- Konsistinte prestaasjes fan reguliere Linux-konteners, ferhege isolaasje sûnder de prestaasjesoverhead fan reguliere VM's
- Eliminearje de needsaak om konteners út te fieren yn folsleine firtuele masines, generyske ynterfaces ferienfâldigje yntegraasje en lansearring
ynstelling
der binne
wichtich: Kata Containers-wurk wurdt allinich stipe op hardware, trochstjoere fan virtualisaasje wurket ek net altyd nedich sse4.1 stipe út de prosessor.
It ynstallearjen fan Kata Containers is frij simpel:
Ynstallearje nutsbedriuwen foar wurkjen mei repositories:
# yum -y install yum-utils
Selinux útskeakelje (it is krekter om te konfigurearjen, mar foar ienfâld skeakelje ik it út):
# setenforce 0
# sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config
Wy ferbine it repository en fiere de ynstallaasje út
# source /etc/os-release
# ARCH=$(arch)
# BRANCH="${BRANCH:-stable-1.10}"
# yum-config-manager --add-repo "http://download.opensuse.org/repositories/home:/katacontainers:/releases:/${ARCH}:/${BRANCH}/CentOS_${VERSION_ID}/home:katacontainers:releases:${ARCH}:${BRANCH}.repo"
# yum -y install kata-runtime kata-proxy kata-shim
oanpassing
Ik sil ynstelle om te wurkjen mei docker, de ynstallaasje is typysk, ik sil it net yn mear detail beskriuwe:
# rpm -qa | grep docker
docker-ce-cli-19.03.6-3.el7.x86_64
docker-ce-19.03.6-3.el7.x86_64
# docker -v
Docker version 19.03.6, build 369ce74a3c
Wy meitsje feroarings oan daemon.json:
# cat <<EOF > /etc/docker/daemon.json
{
"default-runtime": "kata-runtime",
"runtimes": {
"kata-runtime": {
"path": "/usr/bin/kata-runtime"
}
}
}
EOF
Docker opnij starte:
# service docker restart
Funksjonele kontrôle
As jo de kontener begjinne foardat jo docker opnij starte, kinne jo sjen dat uname de ferzje fan 'e kernel sil jaan dy't rint op it haadsysteem:
# docker run busybox uname -a
Linux 19efd7188d06 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64 GNU/Linux
Nei in trochstart sjocht de kernelferzje der sa út:
# docker run busybox uname -a
Linux 9dd1f30fe9d4 4.19.86-5.container #1 SMP Sat Feb 22 01:53:14 UTC 2020 x86_64 GNU/Linux
Mear teams!
# time docker run busybox mount
kataShared on / type 9p (rw,dirsync,nodev,relatime,mmap,access=client,trans=virtio)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,relatime,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (ro,nosuid,nodev,noexec,relatime,xattr,name=systemd)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (ro,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (ro,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (ro,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (ro,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup (ro,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (ro,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/freezer type cgroup (ro,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (ro,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup (ro,nosuid,nodev,noexec,relatime,cpuset)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
kataShared on /etc/resolv.conf type 9p (rw,dirsync,nodev,relatime,mmap,access=client,trans=virtio)
kataShared on /etc/hostname type 9p (rw,dirsync,nodev,relatime,mmap,access=client,trans=virtio)
kataShared on /etc/hosts type 9p (rw,dirsync,nodev,relatime,mmap,access=client,trans=virtio)
proc on /proc/bus type proc (ro,relatime)
proc on /proc/fs type proc (ro,relatime)
proc on /proc/irq type proc (ro,relatime)
proc on /proc/sys type proc (ro,relatime)
tmpfs on /proc/acpi type tmpfs (ro,relatime)
tmpfs on /proc/timer_list type tmpfs (rw,nosuid,size=65536k,mode=755)
tmpfs on /sys/firmware type tmpfs (ro,relatime)
real 0m2.381s
user 0m0.066s
sys 0m0.039s
# time docker run busybox free -m
total used free shared buff/cache available
Mem: 1993 30 1962 0 1 1946
Swap: 0 0 0
real 0m3.297s
user 0m0.086s
sys 0m0.050s
Fast load testen
Om de ferliezen fan virtualisaasje te beoardieljen - ik rinne sysbench, as de wichtichste foarbylden
Sysbench útfiere mei Docker+containerd
Prosessor test
sysbench 1.0: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Prime numbers limit: 20000
Initializing worker threads...
Threads started!
General statistics:
total time: 36.7335s
total number of events: 10000
total time taken by event execution: 36.7173s
response time:
min: 3.43ms
avg: 3.67ms
max: 8.34ms
approx. 95 percentile: 3.79ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 36.7173/0.00
RAM test
sysbench 1.0: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Initializing worker threads...
Threads started!
Operations performed: 104857600 (2172673.64 ops/sec)
102400.00 MiB transferred (2121.75 MiB/sec)
General statistics:
total time: 48.2620s
total number of events: 104857600
total time taken by event execution: 17.4161s
response time:
min: 0.00ms
avg: 0.00ms
max: 0.17ms
approx. 95 percentile: 0.00ms
Threads fairness:
events (avg/stddev): 104857600.0000/0.00
execution time (avg/stddev): 17.4161/0.00
Sysbench útfiere mei Docker + Kata Containers
Prosessor test
sysbench 1.0: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Prime numbers limit: 20000
Initializing worker threads...
Threads started!
General statistics:
total time: 36.5747s
total number of events: 10000
total time taken by event execution: 36.5594s
response time:
min: 3.43ms
avg: 3.66ms
max: 4.93ms
approx. 95 percentile: 3.77ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 36.5594/0.00
RAM test
sysbench 1.0: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 1
Initializing random number generator from current time
Initializing worker threads...
Threads started!
Operations performed: 104857600 (2450366.94 ops/sec)
102400.00 MiB transferred (2392.94 MiB/sec)
General statistics:
total time: 42.7926s
total number of events: 104857600
total time taken by event execution: 16.1512s
response time:
min: 0.00ms
avg: 0.00ms
max: 0.43ms
approx. 95 percentile: 0.00ms
Threads fairness:
events (avg/stddev): 104857600.0000/0.00
execution time (avg/stddev): 16.1512/0.00
Yn prinsipe is de situaasje al dúdlik, mar it is better om de tests ferskate kearen út te fieren, útfallers fuort te heljen en de resultaten te gemiddelden, dus ik doch noch net mear testen.
befinings
Nettsjinsteande it feit dat sokke konteners sa'n fiif oant tsien kear langer duorje om op te starten (typyske runtiid foar ferlykbere kommando's by it brûken fan containerd is minder dan in tredde fan in sekonde), wurkje se noch frij fluch as wy de absolute starttiid nimme (dêr binne hjirboppe foarbylden, kommando's útfierd yn gemiddeld trije sekonden). No, de resultaten fan in flugge test fan CPU en RAM litte hast deselde resultaten sjen, dy't net kinne mar bliid wêze, benammen yn it ljocht fan it feit dat isolaasje wurdt levere mei sa'n goed rinnende meganisme as kvm.
Meidieling
It artikel is in resinsje, mar it jout jo de mooglikheid om te fiele de alternative runtime. In protte gebieten fan tapassing wurde net behannele, bygelyks de side beskriuwt de mooglikheid om Kubernetes boppe op Kata Containers út te fieren. Derneist kinne jo ek in searje tests útfiere rjochte op it finen fan befeiligingsproblemen, it ynstellen fan beheiningen en oare nijsgjirrige dingen.
Ik freegje al dyjingen dy't hjir lêzen en weromdraaid hawwe om mei te dwaan oan 'e enkête, wêrfan takomstige publikaasjes oer dit ûnderwerp ôfhingje.
Allinnich registrearre brûkers kinne meidwaan oan 'e enkête.
Moat ik trochgean mei it publisearjen fan artikels oer Kata Containers?
-
80,0%Ja, skriuw mear!28
-
20,0%Nee, net...7
35 brûkers stimden. 7 brûkers ûntholden har.
Boarne: www.habr.com