{"id":36736,"date":"2019-10-31T22:13:26","date_gmt":"2019-10-31T19:13:26","guid":{"rendered":"https:\/\/prohoster.info\/blog\/istoriya-problemy-perenosa-docker-storage-docker-root\/"},"modified":"2019-10-31T22:13:26","modified_gmt":"2019-10-31T19:13:26","slug":"istoriya-problemy-perenosa-docker-storage-docker-root","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/istoriya-problemy-perenosa-docker-storage-docker-root","title":{"rendered":"Historia e problemit t\u00eb transferimit t\u00eb docker storage (docker root)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Jo m\u00eb von\u00eb se para disa dit\u00ebsh, ishte vendosur q\u00eb n\u00eb nj\u00eb nga server\u00ebt t\u00eb zhvendosej docker storage (dosja ku docker ruan t\u00eb gjitha skedar\u00ebt e konteiner\u00ebve, imazheve) n\u00eb nj\u00eb ndarje t\u00eb ve\u00e7ant\u00eb q\u00eb
\nkishte kapacitet m\u00eb t\u00eb madh. Detyra, dukej se ishte triviale dhe nuk premtuar telashe...
\n<\/a><\/noindex>
\nLe t\u00eb fillojm\u00eb:<\/p>\n

1. Nd\u00ebrpresim dhe vrasim t\u00eb gjitha konteiner\u00ebt e aplikacionit ton\u00eb: <\/p>\n

docker-compose down<\/code><\/pre>\n
\nn\u00ebse ka shum\u00eb konteiner\u00eb dhe ata jan\u00eb n\u00eb compose t\u00eb ndryshme, mund t\u00eb b\u00ebjm\u00eb k\u00ebshtu: <\/p>\n
docker rm -f $(docker ps -q)<\/code><\/pre>\n
\n2. Nd\u00ebrpresim demonin docker: <\/p>\n
systemctl stop docker<\/code><\/pre>\n
\n3. Transferojm\u00eb dosjen n\u00eb vendin e duhur: <\/p>\n
cp -r \/var\/lib\/docker \/docker\/data\/storage<\/code><\/pre>\n
\n4. Njoftojm\u00eb demonin docker t\u00eb shikoj\u00eb n\u00eb drejtorin\u00eb e re. K\u00ebtu ka disa variante: ose p\u00ebrmes flamurit -g i tregojm\u00eb demonit rrug\u00ebn e re, ose konfigurimet e systemd, q\u00eb i kemi p\u00ebrdorur. Ose nj\u00eb simlink. Nuk do t\u00eb zgjatem shum\u00eb mbi k\u00ebt\u00eb, n\u00eb internet ka shum\u00eb<\/a><\/noindex> manuale p\u00ebr transferimin e docker root n\u00eb vendin e ri.<\/p>\n
5. Aktivizojm\u00eb demonin docker, dhe v\u00ebzhgojm\u00eb q\u00eb ai t\u00eb shikoj\u00eb aty ku duhet: <\/p>\n
systemctl status docker<\/code><\/pre>\n
\nN\u00eb nj\u00eb nga rreshtat e daljes, duhet t\u00eb shohim:<\/p>\n
\u251c\u250019493 \/usr\/bin\/dockerd --data-root=\/docker\/data\/storage<\/code><\/pre>\n
\nPasi u siguruam q\u00eb demonit i \u00ebsht\u00eb kaluar opsioni, tani do t\u00eb kontrollojm\u00eb n\u00ebse ai e ka zbatuar at\u00eb (falenderojm\u00eb inkvizitor68sl<\/a><\/noindex>)!<\/p>\n
docker info | awk '\/Root Dir\/ {print $NF}' <\/code><\/pre>\n
\n6. Nis\u00ebm aplikacionin ton\u00eb: <\/p>\n
docker-compose up -d<\/code><\/pre>\n
\n7. Po kontrollojm\u00eb<\/p>\n
Dhe k\u00ebtu fillon gj\u00ebja m\u00eb interesante, SGBD, MQ, gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull! Baza \u00ebsht\u00eb e sh\u00ebndosh\u00eb, gjith\u00e7ka funksionon... p\u00ebrve\u00e7 nginx. Kemi nj\u00eb nd\u00ebrtim tonin t\u00eb nginx me Kerberos dhe kurtesha. Shikimi i log\u00ebve t\u00eb kontejnerit tregoi se nuk mund t\u00eb shkruaj\u00eb n\u00eb \/var\/tmp \u2014 leje e refuzuar. Po e shtrydh me gishta tempullin dhe p\u00ebrpiqem t\u00eb analizoj situat\u00ebn... Si \u00ebsht\u00eb e mundur? Imazhi i Docker-it nuk ka ndryshuar. Pra, ne thjesht kaluam direktorin\u00eb. Gjithmon\u00eb ka funksionuar, dhe papritur... P\u00ebr eksperiment hyra manualisht n\u00eb kontejner dhe ndryshova t\u00eb drejtat p\u00ebr k\u00ebt\u00eb katalog, ishin root, root 755<\/u>, i dhash\u00eb root, root 777<\/u>. Dhe gjith\u00e7ka filloi... N\u00eb kok\u00eb m\u00eb ra mendimi \u2014 nj\u00eb absurditet... Mendova, ndoshta kam l\u00ebn\u00eb di\u00e7ka jasht\u00eb... <\/p>\n
Vendosa se humb\u00ebm t\u00eb drejtat e aksesit p\u00ebr skedar\u00ebt gjat\u00eb transferimit. E ndaluam aplikacionin, demonin e Docker-it, deleteuam direktorin\u00eb e re dhe kryem kopjimin e direktoris\u00eb \/var\/lib\/docker duke p\u00ebrdorur rsync -a<\/code>. <\/p>\n
Mendoj, tani sigurisht q\u00eb gjith\u00e7ka \u00ebsht\u00eb mir\u00eb, ngrem\u00eb Docker-in, aplikacionin.<\/p>\n
Ehe\u2026 problemi mbeti... Sistemi im nervoz, flaka p\u00ebr pak n\u00eb konsol\u00ebn time t\u00eb virtualizuar, ku drejtoj teste t\u00eb ndryshme. Kisha k\u00ebt\u00eb imazh nginx dhe hyra brenda kontejnerit, dhe aty n\u00eb katalogun \/var\/tmp, t\u00eb drejtat ishin root, root 777. Pra, ashtu si\u00e7 kisha vendosur manualisht. Por imazhet jan\u00eb identike! <\/p>\n
Kudo ishte p\u00ebrdorur sistemi i skedar\u00ebve xfs.<\/u><\/p>\n
E krahasova p\u00ebrmes komand\u00ebs <\/p>\n
docker inspect my-nginx:12345<\/code><\/pre>\n
\nT\u00eb gjith\u00eb hash-et jan\u00eb identike, gjith\u00e7ka \u00ebsht\u00eb nj\u00ebsoj. Si n\u00eb server, ashtu edhe n\u00eb virtualizimin tim. E hoqa imazhin lokal nginx dhe e shkarkova p\u00ebrs\u00ebri nga registry, q\u00eb p\u00ebr disa arsye \u00ebsht\u00eb n\u00eb t\u00eb nj\u00ebjt\u00ebn makin\u00eb. Dhe problemi \u00ebsht\u00eb i nj\u00ebjt\u00eb\u2026 Tani m\u00eb \u00ebsht\u00eb nervozuar syt\u00eb e mi.<\/p>\n
Nuk e mbaj mend se \u00e7far\u00eb mendimesh ishin n\u00eb kok\u00ebn time, p\u00ebrve\u00e7 thirrjeve \"AAAAAA\" e t\u00eb tjera. N\u00eb rrug\u00eb \u00ebsht\u00eb ora 4 t\u00eb nat\u00ebs, kam filluar t\u00eb shikoj burimet e docker p\u00ebr t\u00eb kuptuar parimin e hash-it t\u00eb shtresave t\u00eb imazhit. E hape treta cans e energjis\u00eb. Dhe n\u00eb fund, kuptova se hash-i merr n\u00eb konsiderat\u00eb vet\u00ebm skedarin, p\u00ebrmbajtjen e tij, por NUK KAM T\u00cb DREJTAT E QASJES<\/b>! Kuptoni, p\u00ebr nj\u00eb arsye misterioze, t\u00eb drejtat tona jan\u00eb prishur, nd\u00ebrkoh\u00eb q\u00eb selinux \u00ebsht\u00eb \u00e7aktivizuar, acl nuk p\u00ebrdoren, dhe sticky bit nuk \u00ebsht\u00eb aktiv. <\/p>\n
Kisha fshiha imazhin lokal, gjithashtu fshiha imazhin nga registri docker dhe e ngarkoha p\u00ebrs\u00ebri. Dhe gjith\u00e7ka funksionoi. Pra, del se gjat\u00eb transferimit, t\u00eb drejtat ishin prishur, si brenda imazhit lokal, ashtu edhe brenda imazhit q\u00eb ndodhet n\u00eb registrin. Si\u00e7 e thash\u00eb, p\u00ebr disa arsye, ai ishte vendosur n\u00eb t\u00eb nj\u00ebjtin aparat. Dhe si pasoj\u00eb, n\u00eb nj\u00eb katalog \/var\/lib\/docker.<\/p>\n
Dhe duke parashikuar pyetjen, a kemi provuar t\u00eb kthejm\u00eb shikimin e dockers n\u00eb katalogun e vjet\u00ebr \u2014 jo, nuk provuam, p\u00ebr fat t\u00eb keq, rrethanat nuk lejonin. Edhe d\u00ebshira p\u00ebr t\u00eb zbuluar ishte e madhe.<\/p>\n
Pas shkrimit t\u00eb k\u00ebtij artikulli, solucionin e problemit e shoh t\u00eb qart\u00eb, por n\u00eb momentin e analiz\u00ebs nuk dukej ashtu. Sinqerisht k\u00ebrkova n\u00eb Google dhe nuk gjeta situata t\u00eb ngjashme.<\/p>\n
P\u00ebrfundimi: problemi u zgjidh, por arsyen nuk e kuptova =(<\/p>\n
N\u00ebse dikush e di \/ ka iden\u00eb e mundshme t\u00eb arsyjeve t\u00eb k\u00ebtij problemi \u2014 do t\u00eb isha jasht\u00ebzakonisht i lumtur n\u00eb komentet tuaja!
\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u041d\u0435 \u0434\u0430\u043b\u0435\u0435, \u0447\u0435\u043c \u043f\u0430\u0440\u0443 \u0434\u043d\u0435\u0439 \u043d\u0430\u0437\u0430\u0434 \u0431\u044b\u043b\u043e \u0440\u0435\u0448\u0435\u043d\u043e \u043d\u0430 \u043e\u0434\u043d\u043e\u043c \u0438\u0437 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 \u0432\u044b\u043d\u0435\u0441\u0442\u0438 docker storage (\u043a\u0430\u0442\u0430\u043b\u043e\u0433, \u0433\u0434\u0435 \u0434\u043e\u043a\u0435\u0440 \u0445\u0440\u0430\u043d\u0438\u0442 \u0432\u0441\u0435 \u0444\u0430\u0439\u043b\u044b \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432, \u043e\u0431\u0440\u0430\u0437\u043e\u0432) \u043d\u0430 \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u044b\u0439 \u0440\u0430\u0437\u0434\u0435\u043b, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043e\u0431\u043b\u0430\u0434\u0430\u043b \u0431\u043e\u043b\u044c\u0448\u0435\u0439 \u0435\u043c\u043a\u043e\u0441\u0442\u044c\u044e. \u0417\u0430\u0434\u0430\u0447\u0430, \u043a\u0430\u0437\u0430\u043b\u043e\u0441\u044c \u0431\u044b, \u0442\u0440\u0438\u0432\u0438\u0430\u043b\u044c\u043d\u0430\u044f \u0438 \u043d\u0435 \u043f\u0440\u0435\u0434\u0432\u0435\u0449\u0430\u043b\u0430 \u0431\u0435\u0434\u044b\u2026 \u041f\u0440\u0438\u0441\u0442\u0443\u043f\u0430\u0435\u043c: 1. \u041e\u0441\u0442\u0430\u043d\u0430\u0432\u043b\u0438\u0432\u0430\u0435\u043c \u0438 \u0443\u0431\u0438\u0432\u0430\u0435\u043c \u0432\u0441\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b \u043d\u0430\u0448\u0435\u0433\u043e \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f: docker-compose down \u0435\u0441\u043b\u0438 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u043c\u043d\u043e\u0433\u043e, \u0438 \u043e\u043d\u0438 \u0432 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-36736","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Historia e problemit t\u00eb transferimit t\u00eb ruajtjes docker (docker root) | ProHoster","description":"Nuk ka kaluar m\u00eb shum\u00eb se nj\u00eb ose dy dit\u00eb q\u00eb vendos\u00ebm t\u00eb vendosnim ruajtjen e docker-it (direktori ku docker ruan t\u00eb gjitha skedar\u00ebt e konteiner\u00ebve dhe imazheve) n\u00eb nj\u00eb ndarje t\u00eb ve\u00e7ant\u00eb, e cila kishte m\u00eb shum\u00eb kapacitet. Detyra duket e thjesht\u00eb dhe nuk parashikonte ndonj\u00eb telash... Goditja: 1. Ndalim dhe eliminojm\u00eb t\u00eb gjitha konteiner\u00ebt e aplikacionit ton\u00eb: docker-compose down n\u00ebse ka shum\u00eb konteiner\u00eb, dhe ata jan\u00eb n\u00eb","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/istoriya-problemy-perenosa-docker-storage-docker-root","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0418\u0441\u0442\u043e\u0440\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u043f\u0435\u0440\u0435\u043d\u043e\u0441\u0430 docker storage (docker root) | ProHoster","og:description":"\u041d\u0435 \u0434\u0430\u043b\u0435\u0435, \u0447\u0435\u043c \u043f\u0430\u0440\u0443 \u0434\u043d\u0435\u0439 \u043d\u0430\u0437\u0430\u0434 \u0431\u044b\u043b\u043e \u0440\u0435\u0448\u0435\u043d\u043e \u043d\u0430 \u043e\u0434\u043d\u043e\u043c \u0438\u0437 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 \u0432\u044b\u043d\u0435\u0441\u0442\u0438 docker storage (\u043a\u0430\u0442\u0430\u043b\u043e\u0433, \u0433\u0434\u0435 \u0434\u043e\u043a\u0435\u0440 \u0445\u0440\u0430\u043d\u0438\u0442 \u0432\u0441\u0435 \u0444\u0430\u0439\u043b\u044b \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432, \u043e\u0431\u0440\u0430\u0437\u043e\u0432) \u043d\u0430 \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u044b\u0439 \u0440\u0430\u0437\u0434\u0435\u043b, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043e\u0431\u043b\u0430\u0434\u0430\u043b \u0431\u043e\u043b\u044c\u0448\u0435\u0439 \u0435\u043c\u043a\u043e\u0441\u0442\u044c\u044e. \u0417\u0430\u0434\u0430\u0447\u0430, \u043a\u0430\u0437\u0430\u043b\u043e\u0441\u044c \u0431\u044b, \u0442\u0440\u0438\u0432\u0438\u0430\u043b\u044c\u043d\u0430\u044f \u0438 \u043d\u0435 \u043f\u0440\u0435\u0434\u0432\u0435\u0449\u0430\u043b\u0430 \u0431\u0435\u0434\u044b\u2026 \u041f\u0440\u0438\u0441\u0442\u0443\u043f\u0430\u0435\u043c: 1. \u041e\u0441\u0442\u0430\u043d\u0430\u0432\u043b\u0438\u0432\u0430\u0435\u043c \u0438 \u0443\u0431\u0438\u0432\u0430\u0435\u043c \u0432\u0441\u0435 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b \u043d\u0430\u0448\u0435\u0433\u043e \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f: docker-compose down \u0435\u0441\u043b\u0438 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 \u043c\u043d\u043e\u0433\u043e, \u0438 \u043e\u043d\u0438 \u0432","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/istoriya-problemy-perenosa-docker-storage-docker-root","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:13:26+00:00","article:modified_time":"2019-10-31T19:13:26+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"36736","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-22 04:38:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:39:24","updated":"2026-01-22 04:38:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/36736","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=36736"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/36736\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=36736"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=36736"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=36736"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}