ይህ ጽሑፍ እንዴት እንደሚሰራ ይብራራል
ከዶከር ጋር ስለተለመዱ ችግሮች እና መፍትሄዎቻቸው ቀድሞውኑ
ዋና ዋና ባህሪዎች ፡፡
- ከተለየ ኮር ጋር በመስራት አውታረ መረብን ፣ ማህደረ ትውስታን እና I / O ማግለልን በማቅረብ በምናባዊ ማራዘሚያዎች ላይ በመመርኮዝ የሃርድዌር ማግለልን ማስገደድ ይቻላል ።
- ለኢንዱስትሪ ደረጃዎች ድጋፍ OCI (የኮንቴይነር ቅርጸት) ፣ Kubernetes CRI ን ጨምሮ
- የመደበኛ የሊኑክስ ኮንቴይነሮች ወጥነት ያለው አፈጻጸም፣ ከመደበኛ ቪኤምዎች አፈጻጸም በላይ ያለ ማግለል ይጨምራል
- ኮንቴይነሮችን በተሟላ ቨርቹዋል ማሽኖች ውስጥ የማስኬድ አስፈላጊነትን ያስወግዱ፣ አጠቃላይ በይነገጾች ውህደትን እና ማስጀመርን ያቃልላሉ።
ቅንብር
አሉ
ከፍተኛ: የካታ ኮንቴይነሮች ስራ በሃርድዌር ላይ ብቻ ይደገፋል, ምናባዊ ማስተላለፍ ሁልጊዜም አይሰራም sse4.1 ድጋፍ ያስፈልጋቸዋል ከማቀነባበሪያው.
የካታ ኮንቴይነሮችን መጫን በጣም ቀላል ነው፡-
ከማከማቻዎች ጋር ለመስራት መገልገያዎችን ይጫኑ፡-
# yum -y install yum-utils
Selinux ን አሰናክል (ማዋቀሩ የበለጠ ትክክል ነው፣ ግን ለቀላልነት አጠፋዋለሁ)
# setenforce 0
# sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config
ማከማቻውን እናገናኛለን እና መጫኑን እናከናውናለን
# 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
በደንብ ማድረግ
ከዶክተር ጋር ለመስራት እዘጋጃለሁ ፣ መጫኑ የተለመደ ነው ፣ የበለጠ በዝርዝር አልገለፅም
# 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
በ daemon.json ላይ ለውጦችን እናደርጋለን፡-
# cat <<EOF > /etc/docker/daemon.json
{
"default-runtime": "kata-runtime",
"runtimes": {
"kata-runtime": {
"path": "/usr/bin/kata-runtime"
}
}
}
EOF
መትከያውን እንደገና ያስጀምሩ
# service docker restart
የጤና ማረጋገጫ
ዶከርን እንደገና ከመጀመርዎ በፊት መያዣውን ከጀመሩ ፣ uname በዋናው ስርዓት ላይ የሚሰራውን የከርነል ሥሪት እንደሚሰጥ ማየት ይችላሉ-
# 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
እንደገና ከተጀመረ በኋላ የከርነል ሥሪት ይህንን ይመስላል።
# 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
ተጨማሪ ቡድኖች!
# 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
ፈጣን ጭነት ሙከራ
ከቨርቹዋልነት የሚመጡትን ኪሳራዎች ለመገምገም - sysbench ን እንደ ዋና ምሳሌዎች እሰራለሁ
Docker+containerd በመጠቀም sysbench በማሄድ ላይ
ፕሮሰሰር ሙከራ
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 ሙከራ
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 Containersን በመጠቀም sysbench በማሄድ ላይ
ፕሮሰሰር ሙከራ
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 ሙከራ
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
በመርህ ደረጃ, ሁኔታው ቀድሞውኑ ግልጽ ነው, ነገር ግን ፈተናዎችን ብዙ ጊዜ ማካሄድ, የውጭ መከላከያዎችን በማስወገድ እና ውጤቱን በአማካይ ማካሄድ የበለጠ ጥሩ ነው, ስለዚህ እስካሁን ተጨማሪ ሙከራዎችን አላደርግም.
ግኝቶች
ምንም እንኳን እንደነዚህ ያሉ ኮንቴይነሮች ለመጀመር ከአምስት እስከ አስር እጥፍ የሚረዝሙ ጊዜ ቢወስዱም (በተመሳሳይ ትእዛዞች ውስጥ የተለመደው የሩጫ ጊዜ በኮንቴይነር ሲጠቀሙ ከሰከንድ አንድ ሦስተኛ ያነሰ ነው) ፣ ትክክለኛውን የመጀመሪያ ጊዜ ከወሰድን አሁንም በፍጥነት ይሰራሉ (እዚያ) ከላይ ምሳሌዎች ናቸው, ትዕዛዞች በአማካይ በሶስት ሰከንድ ውስጥ ይከናወናሉ). ደህና ፣ የፈጣን የሲፒዩ እና የ RAM ሙከራ ውጤት አንድ አይነት ውጤት ያሳያል ፣ይህም ሊደሰት አይችልም ፣በተለይም እንደ kvm ባሉ በደንብ በሚሰራ ዘዴ በመጠቀም ማግለል ይሰጣል።
ማስታወቂያ
ጽሑፉ ግምገማ ነው፣ ግን አማራጭ የሩጫ ጊዜ እንዲሰማዎት እድል ይሰጥዎታል። ብዙ የመተግበሪያ ቦታዎች አልተሸፈኑም, ለምሳሌ, ጣቢያው በካታ ኮንቴይነሮች ላይ Kubernetes የማስኬድ ችሎታን ይገልጻል. በተጨማሪም፣ የደህንነት ችግሮችን በማግኘት፣ ገደቦችን በማዘጋጀት እና ሌሎች አስደሳች ነገሮች ላይ ያተኮሩ ተከታታይ ሙከራዎችን ማካሄድ ይችላሉ።
እዚህ ያነበቡት እና ያቆሰሉት ሁሉ በዳሰሳ ጥናቱ ላይ እንዲሳተፉ እጠይቃለሁ ፣ በዚህ ርዕስ ላይ የወደፊት ህትመቶች በየትኛው ላይ እንደሚመሰረቱ ።
በዳሰሳ ጥናቱ ውስጥ የተመዘገቡ ተጠቃሚዎች ብቻ መሳተፍ ይችላሉ።
ስለ ካታ ኮንቴይነሮች መጣጥፎችን ማተም መቀጠል አለብኝ?
-
80,0%አዎ፣ የበለጠ ጻፍ!28
-
20,0%አይ፣ አታድርግ…7
35 ተጠቃሚዎች ድምጽ ሰጥተዋል። 7 ተጠቃሚዎች ድምፀ ተአቅቦ አድርገዋል።
ምንጭ: hab.com