Ev gotar dê biaxive ka ew çawa dixebite
Li ser pirsgirêkên hevpar ên Docker û çareseriyên wan jixwe
Taybetmendiyên sereke
- Bi navek veqetandî re dixebitin, bi vî rengî îzolasyona torê, bîranîn û I / O peyda dikin, gengaz e ku meriv bi zorê li ser bingeha dirêjkirina virtualîzasyonê bi zorê karanîna îzolasyona hardware-yê bide xebitandin.
- Piştgiriya standardên pîşesaziyê di nav de OCI (forma konteynerê), Kubernetes CRI
- Performansa domdar a konteynerên Linux-ê yên birêkûpêk, bêyî performansa zêde ya VM-yên birêkûpêk îzolasyon zêde kir
- Pêdiviya avêtina konteyneran di hundurê makîneyên virtual yên bêkêmasî de ji holê rakin, pêwendiyên gelemperî yekbûnê hêsan dikin û didin destpêkirin
mîhengê
Ð • n, Nûh * de
giring: Karê Kata Konteyner tenê li ser hardware tê piştgirî kirin, şandina virtualbûnê her gav naxebite, di heman demê de piştgiriya sse4.1 hewce dike ji processor.
Sazkirina Kata Containers pir hêsan e:
Karûbarên ji bo xebata bi depoyan re saz bikin:
# yum -y install yum-utils
Selinux neçalak bike (ew rasttir e ku meriv mîheng bike, lê ji bo sadebûnê ez wê neçalak bikim):
# setenforce 0
# sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config
Em depoyê girêdidin û sazkirinê pêk tînin
# 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
ligorî
Ez ê wê mîheng bikim ku bi docker re bixebite, sazkirina wê tîpîk e, ez ê wê bi hûrgulî rave nekim:
# 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
Em guhertinan li daemon.json dikin:
# cat <<EOF > /etc/docker/daemon.json
{
"default-runtime": "kata-runtime",
"runtimes": {
"kata-runtime": {
"path": "/usr/bin/kata-runtime"
}
}
}
EOF
Dokerê ji nû ve bidin destpêkirin:
# service docker restart
Testa fînansî
Ger hûn konteynerê berî destpêkirina dokerê ji nû ve bidin dest pê kirin, hûn dikarin bibînin ku uname dê guhertoya kernelê ku li ser pergala sereke dixebite bide:
# 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
Piştî destpêkek nû, guhertoya kernel wiha xuya dike:
# 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
Tîmên bêtir!
# 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
Testkirina barkirina bilez
Ji bo nirxandina windahiyên ji virtualbûnê - ez sysbench, wekî nimûneyên sereke dimeşînim
Sysbench bi karanîna Docker+containerd dimeşîne
test processor
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
test RAM
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 bi karanîna Konteynirên Docker+Kata dimeşîne
test processor
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
test RAM
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
Di prensîbê de, rewş jixwe zelal e, lê çêtir e ku meriv ceribandinan çend caran bimeşîne, derziyan derxîne û encaman navîn bike, ji ber vê yekê ez hîn bêtir ceribandinan nakim.
vebiguherin
Tevî vê rastiyê ku konteynerên weha ji bo destpêkirinê bi qasî pênc-deh carî dirêjtir digirin (dema xebitandina tîpîk ji bo fermanên wekhev dema ku konteyner bikar tînin ji sêyeka saniyeyê kêmtir e), heke em dema destpêkirina bêkêmasî bigirin ew dîsa jî zû dixebitin (li wir mînakên li jor in, emrên ku bi navînî sê çirkeyan têne kirin). Welê, encamên ceribandinek bilez a CPU û RAM-ê hema hema heman encaman destnîşan dikin, ku nekarin lê şa bibin, nemaze ji ber vê yekê ku veqetandin bi karanîna mekanîzmayek wusa baş-rêvebir a wekî kvm tê peyda kirin.
Daxûyanî
Gotar vekolînek e, lê ew fersendê dide we ku hûn dema xebitandina alternatîf hîs bikin. Gelek warên serîlêdanê nayên vegirtin, mînakî, malper îhtîmala xebitandina Kubernetes li ser konteynirên Kata diyar dike. Wekî din, hûn dikarin rêzek ceribandinan jî bimeşînin ku li ser dîtina pirsgirêkên ewlehiyê, danîna sînorkirin û tiştên din ên balkêş têne sekinandin.
Ez ji hemû kesên ku li vir xwendine û vegerandine daxwaz dikim ku beşdarî anketê bibin, ku weşanên paşerojê yên li ser vê mijarê girêdayî wê bibin.
Tenê bikarhênerên qeydkirî dikarin beşdarî anketê bibin.
Ma ez ê berdewam bikim ku gotarên di derbarê Kata Konteyner de biweşînim?
-
80,0%Erê, bêtir binivîse!28
-
20,0%Na, neke…7
35 bikarhêneran deng dan. 7 bikarhêner jî betal bûn.
Source: www.habr.com