ProHoster > Blog > Ma'muriyat > Kata konteynerlarining qisqacha ko'rinishi va o'rnatilishi

Kata konteynerlarining qisqacha ko'rinishi va o'rnatilishi

Kata konteynerlarining qisqacha ko'rinishi va o'rnatilishi
Ushbu maqola qanday ishlashini muhokama qiladi Kata konteynerlari, shuningdek, ularning Docker-ga ulanishining amaliy qismi ham bo'ladi.

Docker bilan umumiy muammolar va ularning echimlari haqida yozilgan edi, bugun men Kata konteynerlaridan amalga oshirishni qisqacha tasvirlab beraman. Kata Containers - bu engil virtual mashinalarga asoslangan xavfsiz konteyner ish vaqti. Ular bilan ishlash boshqa konteynerlar bilan bir xil, ammo qo'shimcha ravishda apparat virtualizatsiya texnologiyasidan foydalangan holda yanada ishonchli izolyatsiya mavjud. Loyiha 2017-yilda, xuddi shu nomdagi hamjamiyat Intel Clear Containers va Hyper.sh RunV-ning eng yaxshi gβ€˜oyalarini birlashtirishni tugatgandan soβ€˜ng boshlandi, shundan soβ€˜ng turli arxitekturalarni, jumladan, AMD64, ARM, IBM p- va z ni qoβ€˜llab-quvvatlash boβ€˜yicha ishlar davom ettirildi. -seriya. Bundan tashqari, QEMU, Firecracker gipervisorlari ichida ish qo'llab-quvvatlanadi va konteyner bilan integratsiya ham mavjud. Kod quyidagi manzilda mavjud GitHub MIT litsenziyasi ostida.

Asosiy xususiyatlar

  • Alohida yadro bilan ishlash, shu bilan tarmoq, xotira va kiritish-chiqarish izolyatsiyasini ta'minlab, virtualizatsiya kengaytmalari asosida apparat izolyatsiyasidan foydalanishga majburlash mumkin.
  • OCI (konteyner formati), Kubernetes CRI kabi sanoat standartlarini qo'llab-quvvatlash
  • Muntazam Linux konteynerlarining barqaror ishlashi, oddiy VM-larning ishlash xarajatlarisiz yuqori izolyatsiya
  • To'liq virtual mashinalar ichida konteynerlarni ishlatish zaruratini yo'q qiling, umumiy interfeyslar integratsiyani va ishga tushirishni soddalashtiradi

sozlama

bor juda ko'p o'rnatish imkoniyatlari, men Centos 7 operatsion tizimiga asoslangan omborlardan o'rnatishni ko'rib chiqaman.
Muhim: Kata konteynerlari ishi faqat apparatda qo'llab-quvvatlanadi, virtualizatsiya uzatish har doim ham ishlamaydi sse4.1 yordamiga muhtoj protsessordan.

Kata konteynerlarini o'rnatish juda oddiy:

Repozitariylar bilan ishlash uchun yordamchi dasturlarni o'rnating:

# yum -y install yum-utils

Selinux-ni o'chirib qo'ying (sozlash to'g'riroq, ammo soddaligi uchun men uni o'chirib qo'yaman):

# setenforce 0
# sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config

Biz omborni ulaymiz va o'rnatishni amalga oshiramiz

# 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

moslashish

Men uni docker bilan ishlash uchun sozlayman, uning o'rnatilishi odatiy hol, men buni batafsil tasvirlamayman:

# 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

Biz daemon.json ga o'zgartirish kiritamiz:

# cat <<EOF > /etc/docker/daemon.json
{
  "default-runtime": "kata-runtime",
  "runtimes": {
    "kata-runtime": {
      "path": "/usr/bin/kata-runtime"
    }
  }
}
EOF

Dockerni qayta ishga tushiring:

# service docker restart

Funktsional test

Agar siz dockerni qayta ishga tushirishdan oldin konteynerni ishga tushirsangiz, uname asosiy tizimda ishlaydigan yadro versiyasini berishini ko'rishingiz mumkin:

# 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

Qayta ishga tushirilgandan so'ng, yadro versiyasi quyidagicha ko'rinadi:

# 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

Ko'proq jamoalar!

# 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

Tez yuk sinovi

Virtualizatsiyadan yo'qotishlarni baholash uchun men asosiy misollar sifatida sysbench-ni ishga tushiraman bu variantni qabul qiling.

Docker+containerd yordamida sysbench-ni ishga tushirish

Protsessor sinovi

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 testi

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

Docker+Kata konteynerlari yordamida sysbench-ni ishga tushirish

Protsessor sinovi

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 testi

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

Printsipial jihatdan vaziyat allaqachon aniq, ammo testlarni bir necha marta o'tkazish, chet elliklarni olib tashlash va natijalarni o'rtachalashtirish maqbulroqdir, shuning uchun men hali ko'proq testlar qilmayman.

topilmalar

Bunday konteynerlarni ishga tushirish uchun besh-o'n baravar ko'proq vaqt ketishiga qaramay (konteynerdan foydalanganda shunga o'xshash buyruqlar uchun odatiy ish vaqti sekundning uchdan biridan kamroq), agar biz mutlaq boshlanish vaqtini olsak (u erda) ular hali ham juda tez ishlaydi. Yuqoridagi misollar, o'rtacha uch soniyada bajariladigan buyruqlar). Xo'sh, protsessor va operativ xotirani tezkor sinovdan o'tkazish natijalari deyarli bir xil natijalarni ko'rsatadi, bu quvonarli emas, ayniqsa izolyatsiya kvm kabi yaxshi ishlaydigan mexanizm yordamida ta'minlanganligi sababli.

E'lon

Maqola sharhdir, lekin u sizga muqobil ish vaqtini his qilish imkoniyatini beradi. Qo'llashning ko'p sohalari qamrab olinmaydi, masalan, sayt Kubernetes-ni Kata konteynerlari ustida ishlatish qobiliyatini tasvirlaydi. Bundan tashqari, siz xavfsizlik muammolarini topish, cheklovlarni o'rnatish va boshqa qiziqarli narsalarni topishga qaratilgan bir qator testlarni ham o'tkazishingiz mumkin.

Bu erda o'qigan va qayta o'rganganlarning barchasidan so'rovnomada ishtirok etishlarini so'rayman, kelajakda ushbu mavzu bo'yicha nashrlar qaysilarga bog'liq bo'ladi.

So'rovda faqat ro'yxatdan o'tgan foydalanuvchilar ishtirok etishlari mumkin. tizimga kirishiltimos.

Kata konteynerlari haqida maqolalar chop etishda davom etishim kerakmi?

  • 80,0%Ha, ko'proq yozing!28

  • 20,0%Yoβ€˜q, qilmang…7

35 foydalanuvchi ovoz berdi. 7 nafar foydalanuvchi betaraf qolgan.

Manba: www.habr.com

a Izoh qo'shish