{"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\/hr\/blog\/administrirovanie\/izuchaem-docker-chast-6-rabota-s-dannymi","title":{"rendered":"U\u010dimo Docker, dio 6: rad s podacima","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>U dana\u0161njem dijelu prijevoda serije materijala o Dockeru razgovarat \u0107emo o radu s podacima. Konkretno o Docker volumenima. U ovim materijalima stalno smo uspore\u0111ivali softverske mehanizme Dockera s razli\u010ditim jestivim analogijama. Ne\u0107emo se udaljiti od ove tradicije ni ovdje. Podaci u Dockeru mogu biti za\u010dini. U svijetu postoji mnogo vrsta za\u010dina, a u Dockeru mnogo na\u010dina za rad s podacima.<\/p>\n<p>\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/438796\/\">Dio 1: osnove<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/439978\/\">Dio 2: termini i koncepti<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/439980\/\">Dio 3: Dockerfile datoteke<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/440658\/\">Dio 4: smanjenje veli\u010dine slika i ubrzanje njihove izrade<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/440660\/\">Dio 5: komande<\/a><\/noindex><br \/>\n\u2192 <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/post\/441574\/\">Dio 6: rad s podacima<\/a><\/noindex><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ruvds\/blog\/441574\/\"><img decoding=\"async\" alt=\"U\u010dimo Docker, dio 6: rad s podacima\" 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 \/>\nPrimijetite da je ovaj materijal pripremljen koriste\u0107i Docker engine verzije 18.09.1 i API verzije <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.docker.com\/engine\/api\/version-history\/\">1.39<\/a><\/noindex>.<\/p>\n<p>Podaci u Dockeru mogu se pohranjivati privremeno ili trajno. Po\u010dnimo s privremenim podacima.<\/p>\n<h2>Privremeno pohranjivanje podataka<\/h2>\n<p>\nU Docker kontejnerima rad s privremenim podacima mo\u017ee se organizirati na dva na\u010dina.<\/p>\n<p>Zadano, datoteke koje kreira aplikacija koja radi unutar kontejnera pohranjuju se u sloju kontejnera koji podr\u017eava pisanje. Da bi ovaj mehanizam funkcionirao, ni\u0161ta posebno nije potrebno postavljati. Dobiva se jeftino i efikasno. Aplikaciji je dovoljno samo pohraniti podatke i nastaviti s radom. Me\u0111utim, kada kontejner prestane postojati, nestaju i podaci pohranjeni na ovaj jednostavan na\u010din.<\/p>\n<p>Za pohranu privremenih datoteka u Dockeru mo\u017ee se iskoristiti jo\u0161 jedno rje\u0161enje koje je prikladno kada je potrebna vi\u0161a razina performansi u usporedbi s onom koja se mo\u017ee posti\u0107i kori\u0161tenjem standardnog mehanizma privremenog pohranjivanja podataka. Ako ne trebate da va\u0161i podaci ostanu du\u017ee od postojanja kontejnera, mo\u017eete povezati tmpfs s kontejnerom \u2014 privremeni skladi\u0161ni prostor koji koristi RAM hosta. To \u0107e ubrzati izvo\u0111enje operacija pisanja i \u010ditanja podataka.<\/p>\n<p>\u010cesto se dogodi da je potrebno pohraniti podatke i nakon \u0161to kontejner prestane postojati. Za to \u0107e nam biti potrebni mehanizmi za trajnu pohranu podataka.<\/p>\n<h2>Trajno pohranjivanje podataka<\/h2>\n<p>\nPostoje dva na\u010dina za produ\u017eenje \u017eivotnog veka podataka izvan \u017eivotnog veka kontejnera. Jedan od na\u010dina uklju\u010duje kori\u0161\u0107enje bind mount tehnologije. Ovim pristupom, na kontejner se mo\u017ee mount-ovati, na primer, stvarna mapa. Podacima koji se nalaze u toj mapi mogu pristupiti i procesi izvan Dockera. Evo kako <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.docker.com\/storage\/volumes\/\">izgleda<\/a><\/noindex> montiranje tmpfs i bind mount tehnologija.<\/p>\n<p><img decoding=\"async\" alt=\"U\u010dimo Docker, dio 6: rad s podacima\" src=\"\/wp-content\/uploads\/2019\/05\/73b9b7fd59b1321edb9f58953285d8d5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Montiranje tmpfs i bind mount<\/i><\/p>\n<p>Nedostaci kori\u0161\u0107enja bind mount tehnologije su u tome \u0161to njenim kori\u0161\u0107enjem ote\u017eava pravljenje rezervnih kopija podataka, migraciju podataka, i zajedni\u010dko kori\u0161\u0107enje podataka me\u0111u vi\u0161e kontejnera. Bolje je koristiti Docker volumene za trajno skladi\u0161tenje podataka.<\/p>\n<h2>Docker volumeni<\/h2>\n<p>\nVolumen je datote\u010dni sistem koji se nalazi na host ma\u0161ini izvan kontejnera. Docker upravlja kreiranjem i upravljanjem volumenima. Evo glavnih osobina Docker volumena:<\/p>\n<ul>\n<li>Oni su sredstvo za trajno skladi\u0161tenje informacija.<\/li>\n<li>Oni su samostalni i odvojeni od kontejnera.<\/li>\n<li>Razli\u010diti kontejneri mogu zajedni\u010dki koristiti.<\/li>\n<li>Oni omogu\u0107avaju efikasno \u010ditanje i pisanje podataka.<\/li>\n<li>Volumene je mogu\u0107e smestiti na resurse udaljenog cloud provajdera.<\/li>\n<li>Mogu se \u0161ifrovati.<\/li>\n<li>Mogu dobiti imena.<\/li>\n<li>Kontejner mo\u017ee unapred napuniti volumen podacima.<\/li>\n<li>Prikladni su za testiranje.<\/li>\n<\/ul>\n<p>\nKao \u0161to vidite, Docker volumeni imaju izvanredne osobine. Hajde da pri\u010damo o tome kako ih kreirati.<\/p>\n<h2>Kreiranje volumena<\/h2>\n<p>\nVolumene mo\u017eete kreirati pomo\u0107u Docker alata ili putem API poziva.<\/p>\n<p>Evo uputstva u Dockerfile-u koje omogu\u0107ava kreiranje volumena prilikom pokretanja kontejnera.<\/p>\n<pre><code class=\"plaintext\">VOLUME \/my_volume<\/code><\/pre>\n<p>\nKada koristite ovakvu instrukciju u Docker-u, nakon kreiranja kontejnera, bi\u0107e kreiran volumen koji sadr\u017ei podatke koji ve\u0107 postoje na datoj lokaciji. Obratite pa\u017enju da vas kreiranje volumena pomo\u0107u Dockerfile-a ne osloba\u0111a obaveze da navedete ta\u010dku montiranja volumena.<\/p>\n<p>Volumene u Dockerfile-u mo\u017eete kreirati i koriste\u0107i JSON format.<\/p>\n<p>Pored toga, volumene mo\u017eete kreirati putem komandne linije tokom rada kontejnera.<\/p>\n<h2>Rad sa volumenima iz komandne linije<\/h2>\n<p><\/p>\n<h3>\u258dKreiranje volumena<\/h3>\n<p>\nSamostalan volumen mo\u017eete kreirati slede\u0107om komandom:<\/p>\n<pre><code class=\"plaintext\">docker volume create --name my_volume<\/code><\/pre>\n<p><\/p>\n<h3>\u258dProvjera informacija o volumenima<\/h3>\n<p>\nDa biste pregledali popis Docker volumena, upotrijebite sljede\u0107u naredbu:<\/p>\n<pre><code class=\"plaintext\">docker volume ls<\/code><\/pre>\n<p>\nIstra\u017eivanje odre\u0111enog volumena mo\u017ee se izvr\u0161iti na sljede\u0107i na\u010din:<\/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 na sljede\u0107i na\u010din:<\/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 kontejnera, mo\u017eete koristiti ovu naredbu:<\/p>\n<pre><code class=\"plaintext\">docker volume prune<\/code><\/pre>\n<p>\nPrije brisanja volumena, Docker \u0107e od vas zatra\u017eiti potvrdu za izvr\u0161enje ove operacije.<\/p>\n<p>Ako je volumen povezan s bilo kojim kontejnerom, taj volumen se ne mo\u017ee obrisati dok se odgovaraju\u0107i kontejner ne izbri\u0161e. \u010cak i ako je kontejner izbrisan, Docker to ne razumije uvijek. Ako se to dogodi, mo\u017eete koristiti sljede\u0107u naredbu:<\/p>\n<pre><code class=\"plaintext\">docker system prune<\/code><\/pre>\n<p>\nOna je namijenjena za \u010di\u0161\u0107enje resursa Dockera. Nakon izvr\u0161enja ove naredbe, trebali biste imati mogu\u0107nost brisanja volumena \u010diji je status prethodno bio pogre\u0161no odre\u0111en.<\/p>\n<h2>Zastavice \u2014mount i \u2014volume<\/h2>\n<p>\nZa rad s volumena \u010desto \u0107ete morati koristiti flageve prilikom pozivanja naredbe. <code>docker<\/code>Na primjer, da biste stvorili volumen tijekom kreiranja kontejnera, mo\u017eete upotrijebiti 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>\nDavno, prije 2017. godine, bio je popularan flag <code>--volume<\/code>. Izvorno je ovaj flag (mo\u017ee se koristiti u skra\u0107enom obliku, tada izgleda kao <code>-v<\/code>) kori\u0161ten za samostalne kontejnere, dok je flag <code>--mount<\/code> bio u okru\u017eenju Docker Swarm. Me\u0111utim, po\u010dev\u0161i od Dockera 17.06, flag <code>--mount<\/code> mo\u017ee se koristiti u svim scenarijima.<\/p>\n<p>Treba napomenuti da se kori\u0161tenjem flageva <code>--mount<\/code> pove\u0107ava koli\u010dina dodatnih podataka koje je potrebno navesti u naredbi, no iz nekoliko razloga, bolje je koristiti taj flag umjesto <code>--volume<\/code>. Oznaka <code>--mount<\/code> -- to je jedini mehanizam koji omogu\u0107ava rad s servisima ili navo\u0111enje parametara drajvera volumena. Osim toga, rad s ovim flagom je jednostavniji.<\/p>\n<p>U postoje\u0107im primjerima naredbi usmjerenih na rad s podacima u Dockeru, mo\u017eete prona\u0107i mnogo primjera kori\u0161tenja flageva <code>-v<\/code>. Poku\u0161avaju\u0107i prilagoditi te naredbe za sebe, imajte na umu da flagevi <code>--mount<\/code> i <code>--volume<\/code> koriste razli\u010dite formate parametara. Dakle, ne mo\u017eete jednostavno zamijeniti <code>-v<\/code> na <code>--mount<\/code> i dobiti radnu naredbu.<\/p>\n<p>Glavna razlika izme\u0111u <code>--mount<\/code> i <code>--volume<\/code> je u tome \u0161to se pri kori\u0161tenju flageva <code>--volume<\/code> svi parametri skupljaju zajedno, u jednom polju, dok se pri kori\u0161tenju <code>--mount<\/code> parametri su odvojeni.<\/p>\n<p>Pri radu s <code>--mount<\/code> parametri su prikazani kao parovi klju\u010d-vrijednost, a to izgleda ovako <code>key=value<\/code>. Ovi parovi su odvojeni zarezima. Evo \u010desto kori\u0161tenih parametara <code>--mount<\/code>:<\/p>\n<ul>\n<li><code>type<\/code> \u2013 vrsta montiranja. Vrijednost odgovaraju\u0107eg klju\u010da 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>. Ovdje govorimo o volumenima, \u0161to zna\u010di da nas zanima vrijednost <code>volume<\/code>.<\/li>\n<li><code>source<\/code> \u2013 izvor montiranja. Za imenovane volumene ovo je naziv volumena. Za neimenovane volumene ovaj klju\u010d nije naveden. Mo\u017ee se skratiti na <code>src<\/code>.<\/li>\n<li><code>destination<\/code> \u2013 putanju na koju se datoteka ili mapa montira unutar kontejnera. Ovaj klju\u010d mo\u017ee se skratiti na <code>dst<\/code> ili <code>cilj<\/code>.<\/li>\n<li><code>readonly<\/code> \u2013 montira volumen koji je namijenjen <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.docker.com\/storage\/volumes\/#use-a-read-only-volume\">samo za \u010ditanje<\/a><\/noindex>. Kori\u0161tenje ovog klju\u010da nije obavezno, vrijednost mu nije dodijeljena.<\/li>\n<\/ul>\n<p>\nEvo primjera upotrebe <code>--mount<\/code> s brojnim parametrima:<\/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\u010dci<\/h2>\n<p>\nEvo korisnih komandi koje mo\u017eete koristiti pri radu s 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 popis \u010desto kori\u0161tenih parametara za <code>--mount<\/code>, primjenjivih u naredbi oblika <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 Dockeru, vrijeme je da ka\u017eemo nekoliko rije\u010di o tome kamo 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> veliki dobar \u010dlanak o Dockeru. <noindex><a rel=\"nofollow\" href=\"https:\/\/www.amazon.com\/Docker-Deep-Dive-Nigel-Poulton-ebook\/dp\/B01LXWQUFF\">Evo<\/a><\/noindex> knjiga o Dockeru (prilikom kupnje ove knjige, poku\u0161ajte nabaviti najnovije izdanje). <noindex><a rel=\"nofollow\" href=\"https:\/\/dockerbook.com\/\">Evo<\/a><\/noindex> jo\u0161 jedna knjiga koja \u0107e odgovarati onima koji smatraju da je praksa najbolji na\u010din u\u010denja tehnologija.<\/p>\n<p><b>Dragi \u010ditatelji!<\/b> Koje biste materijale o Dockeru preporu\u010dili po\u010detnicima?<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/ruvds.com\/ru-rub\/#order\"><img decoding=\"async\" alt=\"U\u010dimo Docker, dio 6: rad s podacima\" 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\/hr\/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=\"hr_HR\" \/>\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\/hr\/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, dio 6: rad s podacima | ProHoster","description":"U dana\u0161njem dijelu prijevoda serije materijala o Dockeru, razgovarat \u0107emo o radu s podacima. Konkretno \u2013 o Docker volumenima.","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/izuchaem-docker-chast-6-rabota-s-dannymi","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","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\/hr\/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\/hr\/wp-json\/wp\/v2\/posts\/32873","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=32873"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/32873\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media\/24642"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=32873"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=32873"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=32873"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}