{"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\/hu\/blog\/administrirovanie\/istoriya-problemy-perenosa-docker-storage-docker-root","title":{"rendered":"A docker t\u00e1rol\u00f3 (docker root) \u00e1tviteli probl\u00e9ma t\u00f6rt\u00e9nete","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>N\u00e9h\u00e1ny nappal ezel\u0151tt \u00fagy d\u00f6nt\u00f6tt\u00fcnk, hogy az egyik szerveren a docker t\u00e1rol\u00f3t (az a mappa, ahol a docker az \u00f6sszes kont\u00e9nerf\u00e1jlt, k\u00e9pet t\u00e1rolja) egy k\u00fcl\u00f6n part\u00edci\u00f3ra helyezz\u00fck, amely <br \/>\nnagyobb kapacit\u00e1ssal rendelkezik. A feladat, l\u00e1tsz\u00f3lag, trivi\u00e1lisnak t\u0171nt, \u00e9s nem \u00edg\u00e9rt semmi rosszat\u2026<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nKezdj\u00fck:<\/p>\n<p>1. Le\u00e1ll\u00edtjuk \u00e9s meg\u00f6l\u00fcnk minden kont\u00e9nert az alkalmaz\u00e1sunkb\u00f3l: <\/p>\n<pre><code class=\"bash\">docker-compose down<\/code><\/pre>\n<p>\nha sok kont\u00e9ner van, \u00e9s k\u00fcl\u00f6nb\u00f6z\u0151 compose-okat haszn\u00e1lnak, akkor \u00edgy: <\/p>\n<pre><code class=\"bash\">docker rm -f $(docker ps -q)<\/code><\/pre>\n<p>\n2. Le\u00e1ll\u00edtjuk a docker d\u00e9mon-t: <\/p>\n<pre><code class=\"bash\">systemctl stop docker<\/code><\/pre>\n<p>\n3. \u00c1thelyezz\u00fck a mapp\u00e1t a megfelel\u0151 helyre: <\/p>\n<pre><code class=\"bash\">cp -r \/var\/lib\/docker \/docker\/data\/storage<\/code><\/pre>\n<p>\n4. \u00c9rtes\u00edtj\u00fck a docker d\u00e9mont, hogy n\u00e9zze az \u00faj k\u00f6nyvt\u00e1rat. Itt van n\u00e9h\u00e1ny lehet\u0151s\u00e9g: vagy a -g kapcsol\u00f3val adjuk meg az \u00faj utat a d\u00e9monnak, vagy a systemd konfigur\u00e1ci\u00f3s f\u00e1jlokat haszn\u00e1ljuk, ahogy mi is tett\u00fck. Vagy szimbolikus link. Err\u0151l nem \u00edrok r\u00e9szletesebben, az interneten <noindex><a rel=\"nofollow\" href=\"https:\/\/linuxconfig.org\/how-to-move-docker-s-default-var-lib-docker-to-another-directory-on-ubuntu-debian-linux\">b\u0151ven<\/a><\/noindex> van k\u00e9zik\u00f6nyv a docker root \u00faj helyre t\u00f6rt\u00e9n\u0151 \u00e1thelyez\u00e9s\u00e9r\u0151l.<\/p>\n<p>5. Ind\u00edtsuk el a docker d\u00e9mont, \u00e9s figyelj\u00fck, hogy hova n\u00e9z: <\/p>\n<pre><code class=\"bash\">systemctl status docker<\/code><\/pre>\n<p>\nA kimenet egyik sor\u00e1ban l\u00e1tnunk kell:<\/p>\n<pre><code class=\"bash\">\u251c\u250019493 \/usr\/bin\/dockerd --data-root=\/docker\/data\/storage<\/code><\/pre>\n<p>\nMeggy\u0151z\u0151dt\u00fcnk arr\u00f3l, hogy a d\u00e9mont\u00f3l megkaptuk a v\u00e1laszt\u00e1si lehet\u0151s\u00e9get, most ellen\u0151rizz\u00fck, hogy alkalmazta-e (k\u00f6sz\u00f6net <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/users\/inkvizitor68sl\/\" class=\"user_link\">inkvizitor68sl<\/a><\/noindex>)!<\/p>\n<pre><code class=\"bash\">docker info | awk '\/Root Dir\/ {print $NF}' <\/code><\/pre>\n<p>\n6. Ind\u00edtsuk el az alkalmaz\u00e1sunkat: <\/p>\n<pre><code class=\"bash\">docker-compose up -d<\/code><\/pre>\n<p>\n7. Ellen\u0151rizz\u00fck<\/p>\n<p>Itt kezd\u0151dik a leg\u00e9rdekesebb r\u00e9sz, az SGBD, MQ, minden rendben! Az adatb\u00e1zis \u00e9pen maradt, minden m\u0171k\u00f6dik\u2026 kiv\u00e9ve az nginx-t. Van egy saj\u00e1t nginx-\u00fcnk Kerberos-szal \u00e9s kurv\u00e1k n\u00e9lk\u00fcl. A kont\u00e9ner napl\u00f3inak \u00e1tn\u00e9z\u00e9se azt mutatta, hogy nem tud \u00edrni a \/var\/tmp k\u00f6nyvt\u00e1rba \u2013 A hozz\u00e1f\u00e9r\u00e9s megtagadva. Pihentetem az ujjaimat a hal\u00e1nt\u00e9komon, \u00e9s pr\u00f3b\u00e1lom analiz\u00e1lni a helyzetet\u2026 Hogyan t\u00f6rt\u00e9nhetett ez? A docker k\u00e9p nem v\u00e1ltozott. Csak a k\u00f6nyvt\u00e1rat helyezt\u00fck \u00e1t. Mindig m\u0171k\u00f6d\u00f6tt, \u00e9s most\u2026 K\u00eds\u00e9rletk\u00e9ppen bel\u00e9ptem a kont\u00e9nerbe, \u00e9s megv\u00e1ltoztattam a jogosults\u00e1gokat a megadott mapp\u00e1hoz, volt<u> root, root 755<\/u>, adtam <u>root, root 777<\/u>. \u00c9s minden elindult\u2026 A fejemben megsz\u00f3lalt egy gondolat \u2013 valami \u0151r\u00fclts\u00e9g\u2026 Gondoltam, tal\u00e1n valamit elfelejtettem\u2026 <\/p>\n<p>\u00dagy d\u00f6nt\u00f6ttem, hogy a f\u00e1jlok hozz\u00e1f\u00e9r\u00e9si jogait elvesztett\u00fck az \u00e1thelyez\u00e9s sor\u00e1n. Le\u00e1ll\u00edtottuk az alkalmaz\u00e1st, a docker d\u00e9mont, t\u00f6r\u00f6lt\u00fck az \u00faj mapp\u00e1t, \u00e9s a \/var\/lib\/docker mappa m\u00e1sol\u00e1s\u00e1t v\u00e9gezt\u00fck <code>rsync -a<\/code>. <\/p>\n<p>Most m\u00e1r biztos vagyok benne, hogy minden rendben lesz, ind\u00edtom a dockert, az alkalmaz\u00e1st.<\/p>\n<p>H\u00e1t\u2026 a probl\u00e9ma megmaradt\u2026 Be volt rekedve a szemem. Elrohantam a virtu\u00e1lis g\u00e9pem konzol\u00e1ra, ahol k\u00fcl\u00f6nf\u00e9le teszteket futtattam, volt ez az nginx k\u00e9p, \u00e9s bel\u00e9ptem a kont\u00e9nerbe, \u00e9s ott a \/var\/tmp mapp\u00e1n a jogosults\u00e1gok root, root 777. Teh\u00e1t ugyanazok, amiket manu\u00e1lisan kellett be\u00e1ll\u00edtanom. De hiszen a k\u00e9pek azonosak! <\/p>\n<p><u>Mindenhol xfs f\u00e1jlrendszert haszn\u00e1ltak.<\/u><\/p>\n<p>\u00d6sszehasonl\u00edtottam a k\u00f6vetkez\u0151 paranccsal <\/p>\n<pre><code class=\"bash\">docker inspect my-nginx:12345<\/code><\/pre>\n<p>\nMinden hash azonos, mind egy az egyben. Ak\u00e1r a szerveren, ak\u00e1r a virtu\u00e1lis g\u00e9pemen. T\u00f6r\u00f6ltem a helyi nginx k\u00e9pet, \u00e9s \u00fajra let\u00f6lt\u00f6ttem a registry-b\u0151l, ami k\u00fcl\u00f6nb\u00f6z\u0151 okok miatt ugyanazon a g\u00e9pen van. \u00c9s ugyanaz a probl\u00e9ma\u2026 Most a m\u00e1sodik szemem is elkezdett remegni.<\/p>\n<p>M\u00e1r nem eml\u00e9kszem, mik j\u00e1rtak a fejemben, a \u201eAAAAAAA\u201d felki\u00e1lt\u00e1son k\u00edv\u00fcl. \u00c9jszaka 4 \u00f3ra van, el\u0151vettem a docker forr\u00e1sk\u00f3dot, hogy meg\u00e9rtsem a r\u00e9teg hash-el\u00e9s\u00e9nek elv\u00e9t. Megnyitottam a harmadik energiaitalos dobozt. \u00c9s v\u00e9g\u00fcl r\u00e1j\u00f6ttem, hogy a hash-el\u00e9s csak a f\u00e1jlt \u00e9s annak tartalm\u00e1t veszi figyelembe, de <b>NEM A HOZZ\u00c1F\u00c9R\u00c9SI JOGOKAT<\/b>! Teh\u00e1t valami rejt\u00e9lyes m\u00f3don a jogosults\u00e1gok megs\u00e9r\u00fcltek, pedig a selinux le volt kapcsolva, az acl nem volt haszn\u00e1lva, sticky bit pedig nem volt. <\/p>\n<p>T\u00f6r\u00f6ltem a helyi k\u00e9pet, t\u00f6r\u00f6ltem a registry-beli k\u00e9pet is \u00e9s \u00fajra felt\u00f6lt\u00f6ttem. \u00c9s minden m\u0171k\u00f6d\u00f6tt. Teh\u00e1t \u00fagy t\u0171nik, hogy a \u00e1tvitel sor\u00e1n a jogosults\u00e1gok megs\u00e9r\u00fcltek, mind a helyi k\u00e9pben, mind a registry-ben tal\u00e1lhat\u00f3 k\u00e9pben. Ahogy m\u00e1r mondtam, k\u00fcl\u00f6nb\u00f6z\u0151 okok miatt itt a g\u00e9pen helyezkedett el. \u00c9s k\u00f6vetkez\u00e9sk\u00e9ppen egy mapp\u00e1ban \/var\/lib\/docker.<\/p>\n<p>\u00c9s el\u0151re l\u00e1tva a k\u00e9rd\u00e9st, nem pr\u00f3b\u00e1ltuk visszaford\u00edtani a dockert a r\u00e9gi mapp\u00e1ba \u2014 nem, sajnos, a k\u00f6r\u00fclm\u00e9nyek nem tett\u00e9k lehet\u0151v\u00e9. De nagyon akartam meg\u00e9rteni.<\/p>\n<p>A cikk meg\u00edr\u00e1sa ut\u00e1n a probl\u00e9ma megold\u00e1sa sz\u00e1momra nyilv\u00e1nval\u00f3nak t\u0171nik, de a k\u00e9rd\u00e9s tiszt\u00e1z\u00e1sa pillanat\u00e1ban nem t\u0171nt annak. \u0150szint\u00e9n keresg\u00e9ltem a neten, \u00e9s nem tal\u00e1ltam hasonl\u00f3 helyzeteket.<\/p>\n<p>\u00d6sszegz\u00e9s: a probl\u00e9m\u00e1t megoldottam, az okot viszont nem \u00e9rtettem meg =(<\/p>\n<p>Ha valaki tudja vagy sejtette, hogy mi lehetett a probl\u00e9ma okainak egyike \u2014 nagyon \u00f6r\u00fcln\u00e9k, ha megosztan\u00e1d a kommentekben!<br \/>\n<br \/>Forr\u00e1s: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/462013\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\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 [&hellip;]<\/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<!-- All in One SEO 5.0.3 - aioseo.com -->\n\t<meta name=\"description\" content=\"\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.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/istoriya-problemy-perenosa-docker-storage-docker-root\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"hu_HU\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\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\" \/>\n\t\t<meta property=\"og:description\" content=\"\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.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/istoriya-problemy-perenosa-docker-storage-docker-root\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:13:26+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:13:26+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47A docker t\u00e1rol\u00f3 (docker root) \u00e1thelyez\u00e9s\u00e9nek probl\u00e9m\u00e1j\u00e1nak t\u00f6rt\u00e9nete | ProHoster","description":"Nem is olyan r\u00e9gen \u00fagy d\u00f6nt\u00f6tt\u00fcnk, hogy az egyik szerveren a docker t\u00e1rol\u00f3t (mappa, ahol a docker t\u00e1rolja az \u00f6sszes kont\u00e9ner \u00e9s k\u00e9p f\u00e1jlj\u00e1t) egy k\u00fcl\u00f6n part\u00edci\u00f3ra helyezz\u00fck, amely nagyobb kapacit\u00e1ssal rendelkezik.","canonical_url":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/istoriya-problemy-perenosa-docker-storage-docker-root","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hu_HU","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.","og:url":"https:\/\/prohoster.info\/hu\/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\/hu\/wp-json\/wp\/v2\/posts\/36736","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/comments?post=36736"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts\/36736\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/media?parent=36736"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/categories?post=36736"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/tags?post=36736"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}