{"id":32873,"date":"2019-10-31T21:49:25","date_gmt":"2019-10-31T18:49:25","guid":{"rendered":"https:\/\/prohoster.info\/blog\/izuchaem-docker-chast-6-rabota-s-dannymi\/"},"modified":"2019-10-31T21:49:25","modified_gmt":"2019-10-31T18:49:25","slug":"izuchaem-docker-chast-6-rabota-s-dannymi","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/izuchaem-docker-chast-6-rabota-s-dannymi","title":{"rendered":"U\u010dimo se Docker, del 6: delo s podatki","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>V dana\u0161nji del serije o Dockerju bomo govorili o delu s podatki. Zlasti o Docker volumnih. V teh materialih smo neprestano primerjali programske mehanizme Dockerja z razli\u010dnimi u\u017eitnimi analogijami. Tudi tukaj ne bomo odstopili od te tradicije. Podatki v Dockerju naj bodo za\u010dimbe. Na svetu je veliko vrst za\u010dimb, prav tako pa tudi v Dockerju obstaja mnogo na\u010dinov ravnanja s podatki.<\/p>\n<p>\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/438796\/\">Del 1: osnove<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/439978\/\">Del 2: izrazi in koncepti<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/439980\/\">Del 3: Dockerfile datoteke<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/440658\/\">Del 4: zmanj\u0161anje velikosti slik in pospe\u0161evanje njihove sestave<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/440660\/\">Del 5: ukazi<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/441574\/\">Del 6: delo s podatki<\/a><\/noindex><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ruvds\/blog\/441574\/\"><img decoding=\"async\" alt=\"U\u010dimo se Docker, del 6: delo s podatki\" src=\"\/wp-content\/uploads\/2019\/05\/b46a9525df1a3ed70d8e2625fbfd42f6.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nUpo\u0161tevajte, da je ta material pripravljen z uporabo Docker motorja razli\u010dice 18.09.1 in API razli\u010dice <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.docker.com\/engine\/api\/version-history\/\">1.39<\/a><\/noindex>.<\/p>\n<p>Podatki v Dockerju se lahko shranjujejo bodisi za\u010dasno bodisi trajno. Za\u010dnimo z za\u010dasnimi podatki.<\/p>\n<h2>Z za\u010dasnim shranjevanjem podatkov<\/h2>\n<p>\nV Docker kontejnerjih lahko organizirate delo z za\u010dasnimi podatki na dva na\u010dina.<\/p>\n<p>Privzeto se datoteke, ki jih ustvari aplikacija, ki deluje v kontejnerju, shranijo v sloju kontejnerja, ki podpira pisanje. Da bi ta mehanizem deloval, ni treba ni\u010desar posebej nastavljati. Enostavno je in ugodno. Aplikaciji je dovolj, da shranite podatke in nadaljuje z delom. Vendar pa, ko kontejner preneha obstajati, izginejo tudi podatki, shranjeni na ta enostaven na\u010din.<\/p>\n<p>Za shranjevanje za\u010dasnih datotek v Dockerju lahko uporabite \u0161e eno re\u0161itev, ki je primerna za tiste primere, ko je potreben vi\u0161ji nivo zmogljivosti v primerjavi s tem, kar je mo\u017eno dose\u010di z uporabo standardnega mehanizma za\u010dasnega shranjevanja podatkov. \u010ce vam neobo\u0161ljnete, da va\u0161i podatki obstajajo dlje, kot obstaja kontejner, lahko priklju\u010dite tmpfs - za\u010dasno skladi\u0161\u010de podatkov, ki uporablja pomnilnik gostitelja. To omogo\u010da pospe\u0161itev operacij branja in pisanja podatkov.<\/p>\n<p>Pogosto se zgodi, da moramo podatke shraniti tudi potem, ko kontejner preneha obstajati. Za to nam bodo koristni mehanizmi trajnega shranjevanja podatkov.<\/p>\n<h2>Trajno shranjevanje podatkov<\/h2>\n<p>\nObstajajo dva na\u010dina, kako podalj\u0161ati \u017eivljenjsko dobo podatkov nad \u017eivljenjsko dobo kontejnerja. Ena od metod je uporaba tehnologije bind mount. S tem pristopom lahko v kontejner priklju\u010dite na primer dejansko obstoje\u010do mapo. Z podatki, shranjenimi v tej mapi, lahko upravljajo tudi procesi zunaj Dockerja. Tako to <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.docker.com\/storage\/volumes\/\">izgleda<\/a><\/noindex> montiranje tmpfs in tehnologija bind mount.<\/p>\n<p><img decoding=\"async\" alt=\"U\u010dimo se Docker, del 6: delo s podatki\" src=\"\/wp-content\/uploads\/2019\/05\/73b9b7fd59b1321edb9f58953285d8d5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Montiranje tmpfs in bind mount<\/i><\/p>\n<p>Slabosti uporabe tehnologije bind mount so v tem, da ote\u017euje varnostno kopiranje podatkov, migracijo podatkov in skupno rabo podatkov med ve\u010d kontejnerji. Za trajno shranjevanje podatkov je veliko bolje uporabiti Docker volumne.<\/p>\n<h2>Docker volumni<\/h2>\n<p>\nVolumen je datote\u010dni sistem, ki se nahaja na gostiteljskem ra\u010dunalniku izven kontejnerjev. Ustvarjanje in upravljanje volumov poteka preko Dockra. Tukaj so glavne lastnosti Docker volumov:<\/p>\n<ul>\n<li>Predstavljajo sredstva za trajno shranjevanje informacij.<\/li>\n<li>So samostojni in lo\u010deni od kontejnerjev.<\/li>\n<li>Lahko jih so\u010dasno uporabljajo razli\u010dni kontejnerji.<\/li>\n<li>Omogo\u010dajo u\u010dinkovito branje in pisanje podatkov.<\/li>\n<li>Volumne lahko shranjujete na virih oddanega oblaka.<\/li>\n<li>Lahko jih \u0161ifrirate.<\/li>\n<li>Lahko jim daste imena.<\/li>\n<li>Kontejner lahko pripravi volumen z napolnjenimi podatki vnaprej.<\/li>\n<li>So priro\u010dni za testiranje.<\/li>\n<\/ul>\n<p>\nKot vidite, imajo Docker volumni izjemne lastnosti. Pogovorimo se o tem, kako jih ustvariti.<\/p>\n<h2>Ustvarjanje volumov<\/h2>\n<p>\nVolumne lahko ustvarite z orodji Docker ali s pozivi API.<\/p>\n<p>Tukaj je navodilo v Dockerfile, ki omogo\u010da ustvarjanje volumna ob zagonu kontejnerja.<\/p>\n<pre><code class=\"plaintext\">VOLUME \/my_volume<\/code><\/pre>\n<p>\nZ uporabo takega ukaza Docker po ustvarjanju kontejnerja ustvari volumen, ki vsebuje podatke, ki \u017ee obstajajo na navedenem mestu. Upo\u0161tevajte, da ustvarjanje volumna z uporabo Dockerfile ne odve\u017ee od potrebe po dolo\u010ditvi to\u010dke priklju\u010ditve volumna.<\/p>\n<p>Volumne v Dockerfile lahko ustvarite tudi z uporabo JSON formata.<\/p>\n<p>Poleg tega lahko volumne ustvarite z ukazno vrstico med delovanjem kontejnerja.<\/p>\n<h2>Delo z volumni iz ukazne vrstice<\/h2>\n<p><\/p>\n<h3>\u258dUstvarjanje volumna<\/h3>\n<p>\nSamostojen volumen lahko ustvarite z naslednjim ukazom:<\/p>\n<pre><code class=\"plaintext\">docker volume create --name my_volume<\/code><\/pre>\n<p><\/p>\n<h3>\u258dPreverjanje informacij o volumnu<\/h3>\n<p>\nDa bi ste pregledali listu Docker volumena, koristite slede\u0107u komandu:<\/p>\n<pre><code class=\"plaintext\">docker volume ls<\/code><\/pre>\n<p>\nIstra\u017eivanje konkretnog volumena mo\u017ee se izvr\u0161iti ovako:<\/p>\n<pre><code class=\"plaintext\">docker volume inspect my_volume<\/code><\/pre>\n<p><\/p>\n<h3>\u258dBrisanje volumena<\/h3>\n<p>\nVolumen se mo\u017ee obrisati ovako:<\/p>\n<pre><code class=\"plaintext\">docker volume rm my_volume<\/code><\/pre>\n<p>\nDa biste obrisali sve volumene koji se ne koriste od strane kontejnera, mo\u017eete koristiti slede\u0107u komandu:<\/p>\n<pre><code class=\"plaintext\">docker volume prune<\/code><\/pre>\n<p>\nPre nego \u0161to obri\u0161ete volumene, Docker \u0107e vas zatra\u017eiti potvrdu za izvr\u0161enje ove operacije.<\/p>\n<p>Ako je volumen povezan sa nekim kontejnerom, takav volumen se ne mo\u017ee obrisati sve dok odgovaraju\u0107i kontejner nije obrisan. \u010cak i ako je kontejner obrisan, Docker to ne razume uvek. Ako se to desi \u2014 mo\u017eete koristiti slede\u0107u komandu:<\/p>\n<pre><code class=\"plaintext\">docker system prune<\/code><\/pre>\n<p>\nOna je namenjena za \u010di\u0161\u0107enje Docker resursa. Nakon izvr\u0161enja ove komande, trebalo bi da dobijete mogu\u0107nost da obri\u0161ete volumene \u010diji je status ranije bio pogre\u0161no definisan.<\/p>\n<h2>Flags \u2014mount and \u2014volume<\/h2>\n<p>\nZa rad sa volumenima, prilikom pozivanja komande <code>docker<\/code>, \u010desto \u0107ete morati koristiti flagove. Na primer, da biste kreirali volumen tokom kreiranja kontejnera, mo\u017eete koristiti ovu konstrukciju:<\/p>\n<pre><code class=\"plaintext\">docker container run --mount source=my_volume, target=\/container\/path\/for\/volume my_image<\/code><\/pre>\n<p>\nU pro\u0161losti (pre 2017. godine) popularan je bio flag <code>--volume<\/code>. Ovaj flag (mo\u017ee se koristiti i u skra\u0107enom obliku, tada izgleda kao <code>-v<\/code>) se prvo koristio za samostalne kontejnere, dok je flag <code>--mount<\/code> bio namenjen za Docker Swarm okru\u017eenje. Me\u0111utim, po\u010dev\u0161i od Docker 17.06, flag <code>--mount<\/code> mo\u017ee se koristiti u svim scenarijima.<\/p>\n<p>Treba napomenuti da prilikom kori\u0161\u0107enja flaga <code>--mount<\/code> pove\u0107ava se obim dodatnih podataka koje je potrebno navesti u komandi, ali iz vi\u0161e razloga, bolje je koristiti ovaj flag, umesto <code>--volume<\/code>. Zastavica <code>--mount<\/code> \u2014 to je jedini mehanizam koji omogu\u0107ava rad sa servisima ili definisanje parametara drivera volumena. Pored toga, rad sa ovim flagom je jednostavniji.<\/p>\n<p>U postoje\u0107im primerima komandi usmerenim na rad sa podacima u Dockeru, mo\u017eete prona\u0107i mno\u0161tvo primera kori\u0161\u0107enja flaga <code>-v<\/code>. Poku\u0161avaju\u0107i da prilagodite ove komande sebi, imajte na umu da flagovi <code>--mount<\/code> in <code>--volume<\/code> koriste razli\u010dite formate parametara. To jest, ne mo\u017eete jednostavno zameniti <code>-v<\/code> na <code>--mount<\/code> i dobiti radnu komandu.<\/p>\n<p>Glavna razlika izme\u0111u <code>--mount<\/code> in <code>--volume<\/code> se sastoji u tome \u0161to prilikom kori\u0161\u0107enja flaga <code>--volume<\/code> svi parametri se skupljaju zajedno, u jednom polju, dok se pri kori\u0161\u0107enju <code>--mount<\/code> parametri se odvajaju.<\/p>\n<p>Pri pr\u00e1ci s <code>--mount<\/code> parametri su predstavljeni kao parovi klju\u010d-vrednost, naime, izgleda kao <code>key=value<\/code>. Ovi parovi su odvojeni zarezima. Evo \u010desto kori\u0161\u0107enih parametara <code>--mount<\/code>:<\/p>\n<ul>\n<li><code>type<\/code> \u2014 tip montiranja. Vrednost za odgovaraju\u0107i klju\u010d mo\u017ee biti <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.docker.com\/storage\/bind-mounts\/\">bind<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.docker.com\/storage\/volumes\/\">volume<\/a><\/noindex> ili <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.docker.com\/storage\/tmpfs\/\">tmpfs<\/a><\/noindex>. Ovde govorimo o volumenu, tj. zanimaju nas vrednosti <code>volume<\/code>.<\/li>\n<li><code>source<\/code> \u2014 izvor montiranja. Za imenovane volumene to je \u2014 ime volumena. Za neimenovane volumene ovaj klju\u010d se ne navodi. Mo\u017ee biti skra\u0107en na <code>src<\/code>.<\/li>\n<li><code>cilj<\/code> \u2014 putanju na koju se fajl ili folder montira u kontejneru. Ovaj klju\u010d mo\u017ee biti skra\u0107en na <code>dst<\/code> ili <code>target<\/code>.<\/li>\n<li><code>readonly<\/code> \u2014 montira volumen koji je predvi\u0111en <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.docker.com\/storage\/volumes\/#use-a-read-only-volume\">samo za branje<\/a><\/noindex>. Ovaj klju\u010d nije obavezan, vrednost mu nije dodeljena.<\/li>\n<\/ul>\n<p>\nEvo primera kori\u0161\u0107enja <code>--mount<\/code> sa mno\u0161tvom parametara:<\/p>\n<pre><code class=\"plaintext\">docker run --mount type=volume,source=volume_name,destination=\\\/path\\\/in\\\/container,readonly my_image<\/code><\/pre>\n<p><\/p>\n<h2>Zaklju\u010dki<\/h2>\n<p>\nEvo korisnih komandi koje mo\u017eete koristiti prilikom rada sa Docker volumenima:<\/p>\n<ul>\n<li><code>docker volume create<\/code><\/li>\n<li><code>docker volume ls<\/code><\/li>\n<li><code>docker volume inspect<\/code><\/li>\n<li><code>docker volume rm<\/code><\/li>\n<li><code>docker volume prune<\/code><\/li>\n<\/ul>\n<p>\nEvo liste \u010desto kori\u0161\u0107enih parametara za <code>--mount<\/code>, koji se primenjuju u komandi poput <code>docker run --mount my_options my_image<\/code>:<\/p>\n<ul>\n<li><code>type=volume<\/code><\/li>\n<li><code>source=volume_name<\/code><\/li>\n<li><code>destination=\\\/path\\\/in\\\/container<\/code><\/li>\n<li><code>readonly<\/code><\/li>\n<\/ul>\n<p>\nSada, kada smo zavr\u0161ili ovu seriju materijala o Docker-u, vreme je da ka\u017eemo nekoliko re\u010di o tome kuda se dalje mogu kretati oni koji u\u010de Docker. <noindex><a rel=\"nofollow\" href=\"https:\/\/medium.freecodecamp.org\/a-beginner-friendly-introduction-to-containers-vms-and-docker-79a9e3e119b\">Evo<\/a><\/noindex> dobar glavni \u010dlanak o Docker-u. <noindex><a rel=\"nofollow\" href=\"https:\/\/www.amazon.com\/Docker-Deep-Dive-Nigel-Poulton-ebook\/dp\/B01LXWQUFF\">Evo<\/a><\/noindex> knjiga o Docker-u (prilikom kupovine ove knjige, poku\u0161ajte da dobijete najnovije izdanje). <noindex><a rel=\"nofollow\" href=\"https:\/\/dockerbook.com\/\">Evo<\/a><\/noindex> jo\u0161 jedna knjiga koja \u0107e odgovarati onima koji veruju da je praksa najbolji na\u010din u\u010denja tehnologija.<\/p>\n<p><b>Spo\u0161tovani bralci!<\/b> Koje materijale o Docker-u biste preporu\u010dili novajlijama da prou\u010de?<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/ruvds.com\/ru-rub\/#order\"><img decoding=\"async\" alt=\"U\u010dimo se Docker, del 6: delo s podatki\" src=\"\/wp-content\/uploads\/2019\/05\/78a5dd35cfae6d1e291f175957207436.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<br \/>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ruvds\/blog\/441574\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0439 \u0447\u0430\u0441\u0442\u0438 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0430 \u0441\u0435\u0440\u0438\u0438 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u043e\u0432 \u043e Docker \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 \u0434\u0430\u043d\u043d\u044b\u043c\u0438. \u0412 \u0447\u0430\u0441\u0442\u043d\u043e\u0441\u0442\u0438 \u2014 \u043e \u0442\u043e\u043c\u0430\u0445 Docker. \u0412 \u044d\u0442\u0438\u0445 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u0430\u0445 \u043c\u044b \u043f\u043e\u0441\u0442\u043e\u044f\u043d\u043d\u043e \u0441\u0440\u0430\u0432\u043d\u0438\u0432\u0430\u043b\u0438 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u043d\u044b\u0435 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c\u044b Docker \u0441 \u0440\u0430\u0437\u043d\u044b\u043c\u0438 \u0441\u044a\u0435\u0434\u043e\u0431\u043d\u044b\u043c\u0438 \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u044f\u043c\u0438. \u041d\u0435 \u0431\u0443\u0434\u0435\u043c \u043e\u0442\u0445\u043e\u0434\u0438\u0442\u044c \u043e\u0442 \u044d\u0442\u043e\u0439 \u0442\u0440\u0430\u0434\u0438\u0446\u0438\u0438 \u0438 \u0437\u0434\u0435\u0441\u044c. \u0414\u0430\u043d\u043d\u044b\u0435 \u0432 Docker \u043f\u0443\u0441\u0442\u044c \u0431\u0443\u0434\u0443\u0442 \u0441\u043f\u0435\u0446\u0438\u044f\u043c\u0438. \u0412 \u043c\u0438\u0440\u0435 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u0435\u0442 \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e \u0432\u0438\u0434\u043e\u0432 \u0441\u043f\u0435\u0446\u0438\u0439, \u0430 \u0432 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24642,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-32873","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0439 \u0447\u0430\u0441\u0442\u0438 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0430 \u0441\u0435\u0440\u0438\u0438 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u043e\u0432 \u043e Docker \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 \u0434\u0430\u043d\u043d\u044b\u043c\u0438. \u0412 \u0447\u0430\u0441\u0442\u043d\u043e\u0441\u0442\u0438 \u2014 \u043e \u0442\u043e\u043c\u0430\u0445 Docker.\" \/>\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\/sl\/blog\/administrirovanie\/izuchaem-docker-chast-6-rabota-s-dannymi\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"sl_SI\" \/>\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\u0437\u0443\u0447\u0430\u0435\u043c Docker, \u0447\u0430\u0441\u0442\u044c 6: \u0440\u0430\u0431\u043e\u0442\u0430 \u0441 \u0434\u0430\u043d\u043d\u044b\u043c\u0438 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0439 \u0447\u0430\u0441\u0442\u0438 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0430 \u0441\u0435\u0440\u0438\u0438 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u043e\u0432 \u043e Docker \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 \u0434\u0430\u043d\u043d\u044b\u043c\u0438. \u0412 \u0447\u0430\u0441\u0442\u043d\u043e\u0441\u0442\u0438 \u2014 \u043e \u0442\u043e\u043c\u0430\u0445 Docker.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/izuchaem-docker-chast-6-rabota-s-dannymi\" \/>\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-31T18:49:25+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:49:25+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\udd47U\u010dimo Docker, deo 6: rad sa podacima | ProHoster","description":"U dana\u0161njem delu prevoda serije materijala o Docker-u razgovara\u0107emo o radu sa podacima. Konkretno \u2014 o Docker volumenima.","canonical_url":"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/izuchaem-docker-chast-6-rabota-s-dannymi","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sl_SI","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\u0437\u0443\u0447\u0430\u0435\u043c Docker, \u0447\u0430\u0441\u0442\u044c 6: \u0440\u0430\u0431\u043e\u0442\u0430 \u0441 \u0434\u0430\u043d\u043d\u044b\u043c\u0438 | ProHoster","og:description":"\u0412 \u0441\u0435\u0433\u043e\u0434\u043d\u044f\u0448\u043d\u0435\u0439 \u0447\u0430\u0441\u0442\u0438 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0430 \u0441\u0435\u0440\u0438\u0438 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u043e\u0432 \u043e Docker \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 \u0434\u0430\u043d\u043d\u044b\u043c\u0438. \u0412 \u0447\u0430\u0441\u0442\u043d\u043e\u0441\u0442\u0438 \u2014 \u043e \u0442\u043e\u043c\u0430\u0445 Docker.","og:url":"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/izuchaem-docker-chast-6-rabota-s-dannymi","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-31T18:49:25+00:00","article:modified_time":"2019-10-31T18:49:25+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32873","title":null,"description":null,"keywords":null,"keyphrases":{"focus":[],"additional":[]},"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-21 12:57:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 18:56:03","updated":"2026-08-11 12:50:34","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts\/32873","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/comments?post=32873"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts\/32873\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media\/24642"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media?parent=32873"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/categories?post=32873"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/tags?post=32873"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}