Wannan labarin zai kasance mai ban sha'awa ga masu gwadawa da masu haɓakawa, amma an yi niyya ne musamman ga ƙwararrun ƙwararrun ƙwararru waɗanda ke fuskantar matsalar kafa GitLab CI/CD don gwajin haɗin kai a cikin yanayin rashin isassun kayan more rayuwa da/ko rashin kwantena. dandalin kade-kade. Zan gaya muku yadda ake saita jigilar wuraren gwaji ta amfani da docker rubuta akan mai gudu GitLab harsashi guda ɗaya kuma ta yadda lokacin tura mahalli da yawa, ayyukan da aka ƙaddamar ba su tsoma baki tare da juna ba.
Abubuwa
Bayan Fage
-
A cikin aikina, sau da yawa yakan faru cewa gwajin haɗin kai an "mayar da shi" akan ayyukan. Kuma sau da yawa matsala ta farko kuma mafi mahimmanci ita ce bututun CI, wanda gwajin haɗin kai ana ci gaba ana yin sabis(s) a cikin yanayin dev/stage. Wannan ya haifar da matsaloli kaɗan:
- Saboda lahani a cikin wani sabis na musamman yayin gwajin haɗin kai, za a iya lalata da'irar gwajin ta hanyar karyewar bayanai. Akwai lokuta lokacin aika buƙatu tare da karyewar tsarin JSON ya rushe sabis ɗin, wanda ya sa tsayawar gaba ɗaya baya aiki.
- Ragewar da'irar gwaji yayin da bayanan gwajin ke ƙaruwa. Ina tsammanin ba shi da ma'ana don kwatanta misali tare da tsaftacewa / mirgina baya bayanan. A cikin aikina, ban ci karo da wani aiki ba inda wannan tsari ya gudana cikin kwanciyar hankali.
- Hadarin tarwatsa ayyukan da'irar gwaji lokacin gwada saitunan tsarin gaba ɗaya. Misali, mai amfani/rukuni/password/ manufofin aikace-aikace.
- Bayanan gwaji daga gwaje-gwaje na atomatik yana sa rayuwa ta yi wahala ga masu gwajin hannu.
Wasu za su ce mai kyau autotest ya kamata tsaftace bayanan bayan kansu. Ina da hujja akan:
- Tsayi masu ƙarfi sun dace sosai don amfani.
- Ba kowane abu ba ne za a iya cire shi daga tsarin ta API. Misali, kira don share abu ba a aiwatar da shi ba saboda ya saba wa dabarun kasuwanci.
- Lokacin ƙirƙirar abu ta hanyar API, ana iya ƙirƙira adadi mai yawa na metadata, wanda ke da matsala don sharewa.
- Idan gwaje-gwaje suna da dogaro a tsakanin su, to, tsarin tsaftace bayanan bayan gwaje-gwajen gwaje-gwaje ya juya zuwa ciwon kai.
- Ƙarin (kuma, a ganina, ba a barata ba) kira zuwa API.
- Kuma babbar hujja: lokacin da gwajin gwajin ya fara sharewa kai tsaye daga ma'ajin bayanai. Wannan yana jujjuya zuwa filin wasan PK/FK na gaske! Muna ji daga masu haɓakawa: "Na ƙara / cire / sake sawa alama, me yasa aka kama gwajin haɗin kai 100500?"
A ganina, mafi kyawun mafita shine yanayi mai ƙarfi.
- Mutane da yawa suna amfani da docker-compose don gudanar da yanayin gwaji, amma mutane kaɗan ne ke amfani da docker-compose lokacin gudanar da gwajin haɗin kai a cikin CI/CD. Kuma a nan ba na yin la'akari da kubernetes, swarm da sauran dandamali na ƙungiyar kade-kade. Ba kowane kamfani ke da su ba. Zai yi kyau idan docker-compose.yml ya kasance na duniya.
- Ko da muna da namu mai gudu QA, ta yaya za mu tabbatar da cewa ayyukan da aka ƙaddamar ta hanyar docker-compose ba su tsoma baki tare da juna ba?
- Yadda ake tattara rajistan ayyukan da aka gwada?
- Yadda za a tsaftace mai gudu?
Ina da nawa GitLab mai gudu don ayyukana kuma na ci karo da waɗannan tambayoyin yayin haɓakawa to . Fiye da daidai, lokacin gudanar da gwaje-gwajen haɗin kai. A ƙasa za mu magance waɗannan batutuwa ta amfani da misalai daga wannan aikin.
GitLab Shell Runner
Ga mai gudu, Ina ba da shawarar injin kama-da-wane na Linux tare da 4 vCPU, 4 GB RAM, 50 GB HDD.
Akwai bayanai da yawa akan kafa gitlab-mai gudu akan Intanet, don haka a taƙaice:
- Shiga cikin injin ta hanyar SSH
-
Idan kuna da ƙasa da 8 GB RAM, to ina ba da shawarar don kada mai kashe OOM ya zo ya kashe mana ayyukanmu saboda rashin RAM. Wannan na iya faruwa idan an ƙaddamar da ayyuka sama da 5 a lokaci guda. Ayyukan za su ci gaba a hankali, amma a hankali.
Misali tare da OOM kisa
Idan kun gani a cikin ayyukan rajistan ayyukan
bash: line 82: 26474 Killed, sannan kawai aiwatar da mai gudusudo dmesg | grep 26474[26474] 1002 26474 1061935 123806 339 0 0 java Out of memory: Kill process 26474 (java) score 127 or sacrifice child Killed process 26474 (java) total-vm:4247740kB, anon-rss:495224kB, file-rss:0kB, shmem-rss:0kBKuma idan hoton yayi kama da wannan, to ko dai a ƙara swap ko ƙara RAM.
- Shigar , , , yi.
- Ƙara mai amfani
gitlab-runnerga rukunindockersudo groupadd docker sudo usermod -aG docker gitlab-runner - gitlab-mai gudu.
-
Bude don gyarawa
/etc/gitlab-runner/config.tomlkuma ƙaraconcurrent=20 [[runners]] request_concurrency = 10Wannan zai ba ku damar gudanar da ayyuka masu kama da juna akan mai gudu ɗaya. Kara karantawa .
Idan kana da injin da ya fi ƙarfin, misali 8 vCPU, 16 GB RAM, to waɗannan lambobin za a iya sanya su aƙalla sau 2 girma. Amma duk ya dogara da ainihin abin da za a ƙaddamar da shi a kan wannan mai gudu kuma a cikin wane adadi.
Ya isa.
Ana shirya docker-compose.yml
Babban aikin shine docker-compose.yml na duniya, wanda masu haɓakawa / masu gwadawa zasu iya amfani da su a cikin gida da kuma a cikin bututun CI.
Da farko, muna yin sunayen sabis na musamman don CI. Ɗaya daga cikin keɓantattun masu canji a cikin GitLab CI shine m CI_JOB_ID. Idan ka saka container_name tare da ma'ana "service-${CI_JOB_ID:-local}", sannan a cikin hali:
- idan
CI_JOB_IDba a ayyana shi a cikin masu canjin yanayi,
to sunan sabis zai kasanceservice-local - idan
CI_JOB_IDan bayyana shi a cikin masu canjin yanayi (misali 123),
to sunan sabis zai kasanceservice-123
Na biyu, muna ƙirƙirar hanyar sadarwa gama gari don ayyukan da aka ƙaddamar. Wannan yana ba mu keɓewar matakin cibiyar sadarwa yayin gudanar da mahallin gwaji da yawa.
networks:
default:
external:
name: service-network-${CI_JOB_ID:-local}A gaskiya, wannan shine mataki na farko na nasara =)
Misali na docker-compose.yml tare da sharhi
version: "3"
# Для корректной работы web (php) и fmt нужно,
# чтобы контейнеры имели общий исполняемый контент.
# В нашем случае, это директория /var/www/testrail
volumes:
static-content:
# Изолируем окружение на сетевом уровне
networks:
default:
external:
name: testrail-network-${CI_JOB_ID:-local}
services:
db:
image: mysql:5.7.22
# Каждый container_name содержит ${CI_JOB_ID:-local}
container_name: "testrail-mysql-${CI_JOB_ID:-local}"
environment:
MYSQL_HOST: db
MYSQL_DATABASE: mydb
MYSQL_ROOT_PASSWORD: 1234
SKIP_GRANT_TABLES: 1
SKIP_NETWORKING: 1
SERVICE_TAGS: dev
SERVICE_NAME: mysql
networks:
- default
migration:
image: registry.gitlab.com/touchbit/image/testrail/migration:latest
container_name: "testrail-migration-${CI_JOB_ID:-local}"
links:
- db
depends_on:
- db
networks:
- default
fpm:
image: registry.gitlab.com/touchbit/image/testrail/fpm:latest
container_name: "testrail-fpm-${CI_JOB_ID:-local}"
volumes:
- static-content:/var/www/testrail
links:
- db
networks:
- default
web:
image: registry.gitlab.com/touchbit/image/testrail/web:latest
container_name: "testrail-web-${CI_JOB_ID:-local}"
# Если переменные TR_HTTP_PORT или TR_HTTPS_PORTS не определены,
# то сервис поднимается на 80 и 443 порту соответственно.
ports:
- ${TR_HTTP_PORT:-80}:80
- ${TR_HTTPS_PORT:-443}:443
volumes:
- static-content:/var/www/testrail
links:
- db
- fpm
networks:
- defaultMisalin gudu na gida
docker-compose -f docker-compose.yml up -d
Starting testrail-mysql-local ... done
Starting testrail-migration-local ... done
Starting testrail-fpm-local ... done
Recreating testrail-web-local ... doneAmma ba komai ba ne mai sauƙi tare da ƙaddamarwa a cikin CI.
Ana shirya Makefile
Ina amfani da Makefile saboda yana da matukar dacewa duka don sarrafa yanayin gida da kuma a cikin CI. Karin sharhi akan layi
# У меня в проектах все вспомогательные вещи лежат в директории `.indirect`,
# в том числе и `docker-compose.yml`
# Использовать bash с опцией pipefail
# pipefail - фейлит выполнение пайпа, если команда выполнилась с ошибкой
SHELL=/bin/bash -o pipefail
# Останавливаем контейнеры и удаляем сеть
docker-kill:
docker-compose -f $${CI_JOB_ID:-.indirect}/docker-compose.yml kill
docker network rm network-$${CI_JOB_ID:-testrail} || true
# Предварительно выполняем docker-kill
docker-up: docker-kill
# Создаем сеть для окружения
docker network create network-$${CI_JOB_ID:-testrail}
# Забираем последние образы из docker-registry
docker-compose -f $${CI_JOB_ID:-.indirect}/docker-compose.yml pull
# Запускаем окружение
# force-recreate - принудительное пересоздание контейнеров
# renew-anon-volumes - не использовать volumes предыдущих контейнеров
docker-compose -f $${CI_JOB_ID:-.indirect}/docker-compose.yml up --force-recreate --renew-anon-volumes -d
# Ну и, на всякий случай, вывести что там у нас в принципе запущено на машинке
docker ps
# Коллектим логи сервисов
docker-logs:
mkdir ./logs || true
docker logs testrail-web-$${CI_JOB_ID:-local} >& logs/testrail-web.log
docker logs testrail-fpm-$${CI_JOB_ID:-local} >& logs/testrail-fpm.log
docker logs testrail-migration-$${CI_JOB_ID:-local} >& logs/testrail-migration.log
docker logs testrail-mysql-$${CI_JOB_ID:-local} >& logs/testrail-mysql.log
# Очистка раннера
docker-clean:
@echo Останавливаем все testrail-контейнеры
docker kill $$(docker ps --filter=name=testrail -q) || true
@echo Очистка докер контейнеров
docker rm -f $$(docker ps -a -f --filter=name=testrail status=exited -q) || true
@echo Очистка dangling образов
docker rmi -f $$(docker images -f "dangling=true" -q) || true
@echo Очистка testrail образов
docker rmi -f $$(docker images --filter=reference='registry.gitlab.com/touchbit/image/testrail/*' -q) || true
@echo Очистка всех неиспользуемых volume
docker volume rm -f $$(docker volume ls -q) || true
@echo Очистка всех testrail сетей
docker network rm $(docker network ls --filter=name=testrail -q) || true
docker ps
Duba
yin docker-up
$ make docker-up
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml kill
Killing testrail-web-local ... done
Killing testrail-fpm-local ... done
Killing testrail-mysql-local ... done
docker network rm network-${CI_JOB_ID:-testrail} || true
network-testrail
docker network create network-${CI_JOB_ID:-testrail}
d2ec063324081c8bbc1b08fd92242c2ea59d70cf4025fab8efcbc5c6360f083f
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml pull
Pulling db ... done
Pulling migration ... done
Pulling fpm ... done
Pulling web ... done
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml up --force-recreate --renew-anon-volumes -d
Recreating testrail-mysql-local ... done
Recreating testrail-fpm-local ... done
Recreating testrail-migration-local ... done
Recreating testrail-web-local ... done
docker ps
CONTAINER ID PORTS NAMES
a845d3cb0e5a 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp testrail-web-local
19d8ef001398 9000/tcp testrail-fpm-local
e28840a2369c 3306/tcp, 33060/tcp testrail-migration-local
0e7900c23f37 3306/tcp testrail-mysql-local
yi docker-logs
$ make docker-logs
mkdir ./logs || true
mkdir: cannot create directory ‘./logs’: File exists
docker logs testrail-web-${CI_JOB_ID:-local} >& logs/testrail-web.log
docker logs testrail-fpm-${CI_JOB_ID:-local} >& logs/testrail-fpm.log
docker logs testrail-migration-${CI_JOB_ID:-local} >& logs/testrail-migration.log
docker logs testrail-mysql-${CI_JOB_ID:-local} >& logs/testrail-mysql.log
Ana shirya .gitlab-ci.yml
Gudun gwajin haɗin kai
Integration:
stage: test
tags:
- my-shell-runner
before_script:
# Аутентифицируемся в registry
- docker login -u gitlab-ci-token -p ${CI_JOB_TOKEN} ${CI_REGISTRY}
# Генерируем псевдоуникальные TR_HTTP_PORT и TR_HTTPS_PORT
- export TR_HTTP_PORT=$(shuf -i10000-60000 -n1)
- export TR_HTTPS_PORT=$(shuf -i10000-60000 -n1)
# создаем директорию с идентификатором задачи
- mkdir ${CI_JOB_ID}
# копируем в созданную директорию наш docker-compose.yml
# чтобы контекст был разный для каждой задачи
- cp .indirect/docker-compose.yml ${CI_JOB_ID}/docker-compose.yml
script:
# поднимаем наше окружение
- make docker-up
# запускаем тесты исполняемым jar (у меня так)
- java -jar itest.jar --http-port ${TR_HTTP_PORT} --https-port ${TR_HTTPS_PORT}
# или в контейнере
- docker run --network=testrail-network-${CI_JOB_ID:-local} --rm itest
after_script:
# собираем логи
- make docker-logs
# останавливаем окружение
- make docker-kill
artifacts:
# сохраняем логи
when: always
paths:
- logs
expire_in: 30 daysSakamakon gudanar da irin wannan aikin, kundin rajistan ayyukan a cikin kayan tarihi zai ƙunshi sabis da rajistan ayyukan gwaji. Wanda ya dace sosai idan akwai kurakurai. Kowane gwaji a layi daya yana rubuta nasa log, amma zan yi magana game da wannan daban.
Tsaftace mai gudu
Za a ƙaddamar da aikin bisa ga jadawali kawai.
stages:
- clean
- build
- test
Clean runner:
stage: clean
only:
- schedules
tags:
- my-shell-runner
script:
- make docker-cleanNa gaba, je zuwa aikinmu na GitLab -> CI / CD -> Jadawalai -> Sabon Jadawalin kuma ƙara sabon jadawalin
sakamakon
Ƙaddamar da ayyuka 4 a GitLab CI
A cikin rajistan ayyukan na ƙarshe tare da gwaje-gwajen haɗin kai muna ganin kwantena daga ayyuka daban-daban
CONTAINER ID NAMES
c6b76f9135ed testrail-web-204645172
01d303262d8e testrail-fpm-204645172
2cdab1edbf6a testrail-migration-204645172
826aaf7c0a29 testrail-mysql-204645172
6dbb3fae0322 testrail-web-204645084
3540f8d448ce testrail-fpm-204645084
70fea72aa10d testrail-mysql-204645084
d8aa24b2892d testrail-web-204644881
6d4ccd910fad testrail-fpm-204644881
685d8023a3ec testrail-mysql-204644881
1cdfc692003a testrail-web-204644793
6f26dfb2683e testrail-fpm-204644793
029e16b26201 testrail-mysql-204644793
c10443222ac6 testrail-web-204567103
04339229397e testrail-fpm-204567103
6ae0accab28d testrail-mysql-204567103
b66b60d79e43 testrail-web-204553690
033b1f46afa9 testrail-fpm-204553690
a8879c5ef941 testrail-mysql-204553690
069954ba6010 testrail-web-204553539
ed6b17d911a5 testrail-fpm-204553539
1a1eed057ea0 testrail-mysql-204553539Ƙarin cikakkun bayanai
$ docker login -u gitlab-ci-token -p ${CI_JOB_TOKEN} ${CI_REGISTRY}
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /home/gitlab-runner/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded
$ export TR_HTTP_PORT=$(shuf -i10000-60000 -n1)
$ export TR_HTTPS_PORT=$(shuf -i10000-60000 -n1)
$ mkdir ${CI_JOB_ID}
$ cp .indirect/docker-compose.yml ${CI_JOB_ID}/docker-compose.yml
$ make docker-up
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml kill
docker network rm testrail-network-${CI_JOB_ID:-local} || true
Error: No such network: testrail-network-204645172
docker network create testrail-network-${CI_JOB_ID:-local}
0a59552b4464b8ab484de6ae5054f3d5752902910bacb0a7b5eca698766d0331
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml pull
Pulling web ... done
Pulling fpm ... done
Pulling migration ... done
Pulling db ... done
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml up --force-recreate --renew-anon-volumes -d
Creating volume "204645172_static-content" with default driver
Creating testrail-mysql-204645172 ...
Creating testrail-mysql-204645172 ... done
Creating testrail-migration-204645172 ... done
Creating testrail-fpm-204645172 ... done
Creating testrail-web-204645172 ... done
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c6b76f9135ed registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 13 seconds ago Up 1 second 0.0.0.0:51148->80/tcp, 0.0.0.0:25426->443/tcp testrail-web-204645172
01d303262d8e registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 16 seconds ago Up 13 seconds 9000/tcp testrail-fpm-204645172
2cdab1edbf6a registry.gitlab.com/touchbit/image/testrail/migration:latest "docker-entrypoint.s…" 16 seconds ago Up 13 seconds 3306/tcp, 33060/tcp testrail-migration-204645172
826aaf7c0a29 mysql:5.7.22 "docker-entrypoint.s…" 18 seconds ago Up 16 seconds 3306/tcp testrail-mysql-204645172
6dbb3fae0322 registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 36 seconds ago Up 22 seconds 0.0.0.0:44202->80/tcp, 0.0.0.0:20151->443/tcp testrail-web-204645084
3540f8d448ce registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 38 seconds ago Up 35 seconds 9000/tcp testrail-fpm-204645084
70fea72aa10d mysql:5.7.22 "docker-entrypoint.s…" 40 seconds ago Up 37 seconds 3306/tcp testrail-mysql-204645084
d8aa24b2892d registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" About a minute ago Up 53 seconds 0.0.0.0:31103->80/tcp, 0.0.0.0:43872->443/tcp testrail-web-204644881
6d4ccd910fad registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" About a minute ago Up About a minute 9000/tcp testrail-fpm-204644881
685d8023a3ec mysql:5.7.22 "docker-entrypoint.s…" About a minute ago Up About a minute 3306/tcp testrail-mysql-204644881
1cdfc692003a registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" About a minute ago Up About a minute 0.0.0.0:44752->80/tcp, 0.0.0.0:23540->443/tcp testrail-web-204644793
6f26dfb2683e registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" About a minute ago Up About a minute 9000/tcp testrail-fpm-204644793
029e16b26201 mysql:5.7.22 "docker-entrypoint.s…" About a minute ago Up About a minute 3306/tcp testrail-mysql-204644793
c10443222ac6 registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 5 hours ago Up 5 hours 0.0.0.0:57123->80/tcp, 0.0.0.0:31657->443/tcp testrail-web-204567103
04339229397e registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 5 hours ago Up 5 hours 9000/tcp testrail-fpm-204567103
6ae0accab28d mysql:5.7.22 "docker-entrypoint.s…" 5 hours ago Up 5 hours 3306/tcp testrail-mysql-204567103
b66b60d79e43 registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 5 hours ago Up 5 hours 0.0.0.0:56321->80/tcp, 0.0.0.0:58749->443/tcp testrail-web-204553690
033b1f46afa9 registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 5 hours ago Up 5 hours 9000/tcp testrail-fpm-204553690
a8879c5ef941 mysql:5.7.22 "docker-entrypoint.s…" 5 hours ago Up 5 hours 3306/tcp testrail-mysql-204553690
069954ba6010 registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 5 hours ago Up 5 hours 0.0.0.0:32869->80/tcp, 0.0.0.0:16066->443/tcp testrail-web-204553539
ed6b17d911a5 registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 5 hours ago Up 5 hours 9000/tcp testrail-fpm-204553539
1a1eed057ea0 mysql:5.7.22 "docker-entrypoint.s…" 5 hours ago Up 5 hours 3306/tcp testrail-mysql-204553539An kammala dukkan ayyuka cikin nasara
Kayan kayan tarihi na ɗawainiya sun ƙunshi sabis da rajistan ayyukan gwaji
Komai yana da kyau, amma akwai nuance. Za a iya soke bututun da karfi yayin da ake gudanar da gwaje-gwajen haɗin kai, wanda a halin da ake ciki ba za a dakatar da kwantena masu gudana ba. Daga lokaci zuwa lokaci kana buƙatar tsaftace mai gudu. Abin takaici, aikin don ingantawa a GitLab CE yana kan matsayi
Amma mun kara kaddamar da wani aiki bisa tsari, kuma babu wanda ya hana mu gudanar da shi da hannu.
Je zuwa aikin mu -> CI / CD -> Jadawalin kuma gudanar da aikin Clean runner
Jimlar:
- Muna da mai gudu harsashi ɗaya.
- Babu sabani tsakanin ayyuka da muhalli.
- Muna gudanar da ayyuka tare da gwaje-gwajen haɗin kai a layi daya.
- Kuna iya gudanar da gwaje-gwajen haɗin kai ko dai a cikin gida ko a cikin akwati.
- Ana tattara rajistan ayyukan sabis da gwaji kuma an haɗa su zuwa aikin bututun.
- Yana yiwuwa a tsaftace mai gudu daga tsoffin hotunan Docker.
Lokacin saita shine ~ 2 hours.
Wannan ke nan, a zahiri. Zan yi farin cikin samun amsa.
source: www.habr.com