{"id":2392,"date":"2026-02-03T14:26:18","date_gmt":"2026-02-03T14:26:18","guid":{"rendered":"https:\/\/ssblog.eu.enginyr.ing\/?p=2392"},"modified":"2026-02-03T14:28:18","modified_gmt":"2026-02-03T14:28:18","slug":"gestionarea-docker-si-a-containerelor-pe-un-vps-cele-mai-bune-practici-pentru-stabilitate-si-performanta","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/gestionarea-docker-si-a-containerelor-pe-un-vps-cele-mai-bune-practici-pentru-stabilitate-si-performanta\/","title":{"rendered":"Gestionarea Docker \u0219i a containerelor pe un VPS: Cele mai bune practici pentru stabilitate \u0219i performan\u021b\u0103"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Containerizarea a schimbat fundamental modul \u00een care sunt implementate aplica\u021biile, oferind promisiunea \u201ebuild once, run anywhere\u201d (construie\u0219te o dat\u0103, ruleaz\u0103 oriunde), care este incredibil de atractiv\u0103 pentru dezvoltatori. Totu\u0219i, realitatea opera\u021bional\u0103 a rul\u0103rii Docker pe un server privat virtual (VPS) este adesea mai pu\u021bin simpl\u0103 dec\u00e2t sugereaz\u0103 tutorialele. \u00cen experien\u021ba noastr\u0103 de gestionare a mii de instan\u021be pentru clien\u021bi, vedem frecvent implement\u0103ri Docker bine inten\u021bionate care se transform\u0103 \u00een co\u0219maruri de stabilitate\u2014consum\u00e2nd tot spa\u021biul de stocare disponibil, ocolind firewall-urile sau declan\u0219\u00e2nd Out of Memory (OOM) Killer, care blocheaz\u0103 \u00eentregul server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">La ServerSpan, abord\u0103m containerizarea cu o filozofie a pragmatismului, nu a hype-ului. Docker este un instrument puternic, dar nu este o baghet\u0103 magic\u0103 ce repar\u0103 o arhitectur\u0103 proast\u0103. Introduce un strat de abstractizare care necesit\u0103 o gestionare riguroas\u0103 a resurselor, log-urilor \u0219i ciclurilor de via\u021b\u0103. Dac\u0103 nu este gestionat corect, acel strat de abstractizare devine o ancor\u0103 grea care trage \u00een jos performan\u021ba VPS-ului t\u0103u.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prima \u00eentrebare: chiar ai nevoie de Docker?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de a discuta <em>cum<\/em> s\u0103 gestion\u0103m Docker, trebuie s\u0103 abord\u0103m <em>c\u00e2nd<\/em> s\u0103 \u00eel folosim. C\u00e2nd clien\u021bii ne abordeaz\u0103 solicit\u00e2nd un mediu Docker-heavy, primul nostru pas este adesea s\u0103 audit\u0103m nevoile lor reale. Containerizarea adaug\u0103 overhead\u2014at\u00e2t \u00een termeni de resurse de sistem (CPU\/RAM context switching), c\u00e2t \u0219i de complexitate administrativ\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 g\u0103zduie\u0219ti un site WordPress standard, un magazin Magento sau o aplica\u021bie PHP simpl\u0103, rularea direct\u0103 pe \u201emetal\u201d (Nginx\/Apache nativ + PHP-FPM) este aproape \u00eentotdeauna mai rapid\u0103, mai stabil\u0103 \u0219i mai u\u0219or de depanat dec\u00e2t \u00eempachetarea \u00een containere. Adesea migr\u0103m clien\u021bii <em>departe<\/em> de swarm-uri Docker complexe \u00eenapoi la stive LEMP native, rezult\u00e2nd c\u00e2\u0219tiguri imediate de performan\u021b\u0103 \u0219i complexitate redus\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cu toate acestea, Docker este indispensabil atunci c\u00e2nd ai nevoie de izolare a dependen\u021belor. Dac\u0103 proiectul t\u0103u necesit\u0103 o versiune specific\u0103, \u00eenvechit\u0103 de Python, o bibliotec\u0103 Node.js predispus\u0103 la conflicte sau o arhitectur\u0103 complex\u0103 de microservicii unde serviciile trebuie s\u0103 comunice f\u0103r\u0103 a polua sistemul de operare gazd\u0103, atunci Docker este alegerea potrivit\u0103. Cheia este s\u0103 \u00eel folose\u0219ti chirurgical, nu ca setare implicit\u0103 pentru orice problem\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Limite de resurse: prevenirea efectului \u201eNoisy Neighbor\u201d<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cea mai comun\u0103 cauz\u0103 a instabilit\u0103\u021bii VPS pe care o \u00eent\u00e2lnim implic\u0103 containerele f\u0103r\u0103 limite de resurse. Implicit, unui container Docker i se permite s\u0103 consume oric\u00e2t de mult RAM \u0219i CPU de pe gazd\u0103 solicit\u0103. Dac\u0103 un container de baz\u0103 de date are o scurgere de memorie (memory leak) sau un proces worker Node.js scap\u0103 de sub control, va consuma agresiv fiecare megabyte de RAM disponibil pe VPS-ul t\u0103u.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">C\u00e2nd se \u00eent\u00e2mpl\u0103 acest lucru, kernelul Linux invoc\u0103 OOM Killer pentru a salva sistemul. Crucial, OOM Killer sacrific\u0103 adesea daemonul SSH sau serviciul de baz\u0103 de date mai \u00eent\u00e2i, l\u0103s\u00e2ndu-te blocat \u00een afara unui server pr\u0103bu\u0219it. Pentru a preveni acest lucru, fiecare container trebuie s\u0103 aib\u0103 limite stricte.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Impunem aceste limite prin fi\u0219ierul <code>docker-compose.yml<\/code> sau flag-uri la runtime. De exemplu, \u00een loc s\u0103 l\u0103s\u0103m un container s\u0103 ruleze liber, definim plafoane explicite:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>deploy:\n  resources:\n    limits:\n      cpus: '0.50'\n      memory: 512M\n    reservations:\n      cpus: '0.25'\n      memory: 256M<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Aceast\u0103 configura\u021bie asigur\u0103 c\u0103, chiar dac\u0103 aplica\u021bia din interiorul containerului func\u021bioneaz\u0103 defectuos, se love\u0219te de un tavan de sticl\u0103 \u00eenainte de a putea destabiliza sistemul de operare gazd\u0103. \u00cen <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">mediile noastre VPS gestionate<\/a>, configur\u0103m aceste limite pe baza capacit\u0103\u021bii totale a serverului, l\u0103s\u00e2nd o \u201ezon\u0103 de siguran\u021b\u0103\u201d de RAM nealocat pentru kernelul gazd\u0103 \u0219i serviciile de sistem esen\u021biale. Un server cu 4GB de RAM nu ar trebui s\u0103 aib\u0103 niciodat\u0103 4GB de containere alocate pe el.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Uciga\u0219ul t\u0103cut: gestionarea log-urilor \u0219i spa\u021biul pe disc<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Epuizarea spa\u021biului pe disc este al doilea mod major de e\u0219ec al mediilor containerizate. Driverul implicit de logging al Docker captureaz\u0103 fluxurile STDOUT \u0219i STDERR ale containerului t\u0103u \u0219i le scrie \u00een fi\u0219iere JSON pe discul gazd\u0103. Problema? Implicit, nu exist\u0103 limit\u0103 de m\u0103rime a fi\u0219ierului \u0219i nicio politic\u0103 de rota\u021bie.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Am v\u0103zut servere cu sute de gigabytes de stocare blocate complet deoarece un container prea vorb\u0103re\u021b (cum ar fi un server web \u00een modul debug) a scris log-uri continuu timp de luni de zile, umpl\u00e2nd discul la 100%. Odat\u0103 ce discul este plin, baza de date nu poate scrie tranzac\u021bii, sistemul nu poate crea fi\u0219iere lock, iar serviciile se pr\u0103bu\u0219esc.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru a preveni acest lucru, configur\u0103m daemonul Docker global s\u0103 roteasc\u0103 log-urile. Aceasta se face modific\u00e2nd <code>\/etc\/docker\/daemon.json<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>{\n  \"log-driver\": \"json-file\",\n  \"log-opts\": {\n    \"max-size\": \"10m\",\n    \"max-file\": \"3\"\n  }\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Aceast\u0103 configura\u021bie limiteaz\u0103 fiecare container la trei fi\u0219iere de log de c\u00e2te 10MB fiecare. Odat\u0103 atins\u0103 limita, cele mai vechi log-uri sunt \u0219terse. Aceast\u0103 schimbare simpl\u0103 de configurare, pe care o aplic\u0103m standard pe instan\u021bele Docker gestionate, salveaz\u0103 terabytes de stocare irosit\u0103 \u0219i nenum\u0103rate ore de downtime.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Gestionarea ciclului de via\u021b\u0103 al containerului<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Un reboot de VPS\u2014fie pentru actualiz\u0103ri de kernel sau mentenan\u021b\u0103\u2014nu ar trebui s\u0103 \u00ee\u021bi strice stiva de aplica\u021bii. Totu\u0219i, mul\u021bi utilizatori ruleaz\u0103 containere folosind comenzi manuale <code>docker run<\/code> f\u0103r\u0103 a defini politici de restart. C\u00e2nd serverul reporne\u0219te, acele containere r\u0103m\u00e2n moarte, iar site-ul web r\u0103m\u00e2ne offline p\u00e2n\u0103 c\u00e2nd un administrator intervine manual.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Impunem utilizarea politicilor de restart pentru toate containerele de produc\u021bie. Flag-urile <code>restart: unless-stopped<\/code> sau <code>restart: always<\/code> asigur\u0103 c\u0103 daemonul Docker reporne\u0219te automat containerul dup\u0103 un reboot sau o pr\u0103bu\u0219ire. Acest lucru transform\u0103 o poten\u021bial\u0103 \u00eentrerupere \u00eentr-o clipire de moment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Totu\u0219i, gestionarea ciclului de via\u021b\u0103 merge dincolo de simpla repornire. Implic\u0103 \u0219i gestionarea actualiz\u0103rilor. \u201eImage drift\u201d (devierea imaginii) apare atunci c\u00e2nd un container ruleaz\u0103 o versiune veche a unei imagini, \u00een timp ce registrul are o versiune patch-uit\u0103. Pentru a gestiona acest lucru \u00een siguran\u021b\u0103, descuraj\u0103m utilizarea tag-ului <code>:latest<\/code> \u00een produc\u021bie. Utilizarea <code>:latest<\/code> face implement\u0103rile imprevizibile\u2014nu \u0219tii niciodat\u0103 exact ce cod ruleaz\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen schimb, fix\u0103m versiunile (de exemplu, <code>nginx:1.21.6-alpine<\/code>). C\u00e2nd este necesar\u0103 o actualizare, actualiz\u0103m tag-ul de versiune \u0219i redeploy-\u0103m. Acest lucru permite rollback-uri u\u0219oare dac\u0103 noua versiune introduce bug-uri. Pentru clien\u021bii pe <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">planurile noastre gestionate<\/a>, ne ocup\u0103m sistematic de aceste salturi de versiune, test\u00e2nd compatibilitatea \u00eenainte de a le aplica \u00een mediul live.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Driverele de stocare \u0219i problema Overlay2<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Docker folose\u0219te un sistem de fi\u0219iere union (de obicei overlay2) pentru a stratifica schimb\u0103rile containerului peste imaginea de baz\u0103. Scrierea datelor direct \u00een stratul inscriptibil al containerului este extrem de ineficient\u0103 \u0219i poate umfla driverul de stocare, cauz\u00e2nd degradarea performan\u021bei I\/O. Tehnic, acest lucru este cunoscut sub numele de overhead \u201eCopy-on-Write\u201d.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Impunem o regul\u0103 strict\u0103: <strong>Datele trebuie s\u0103 tr\u0103iasc\u0103 \u00een volume, nu \u00een containere.<\/strong> Orice director care prime\u0219te scrieri frecvente\u2014directoarele de date ale bazei de date, \u00eenc\u0103rc\u0103rile utilizatorilor, log-urile aplica\u021biei\u2014trebuie montat ca un volum numit sau un bind mount c\u0103tre gazd\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mai mult, monitoriz\u0103m activ <a href=\"https:\/\/www.serverspan.ro\/blog\/de-ce-latimea-de-banda-nelimitata-este-o-minciuna-intelegerea-inodes-a-limitelor-i-o-si-de-ce-site-urile-cu-trafic-mare-mor-pe-hostingul-partajat\/\">utilizarea Inode-urilor<\/a>. Imaginile \u0219i volumele Docker consum\u0103 Inode-uri (indicatori de indexare a fi\u0219ierelor) rapid. Un server ar putea ar\u0103ta 50GB de spa\u021biu liber, dar s\u0103 aib\u0103 zero Inode-uri r\u0103mase, f\u0103c\u00e2nd discul imposibil de scris. Rul\u0103m frecvent sarcini de mentenan\u021b\u0103 <code>docker system prune -a --volumes<\/code> (scriptate cu grij\u0103) pentru a elimina imaginile nefolosite, straturile de build ag\u0103\u021bate \u0219i containerele oprite care aglomereaz\u0103 sistemul de fi\u0219iere.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Re\u021belistica \u0219i capcana ocolirii firewall-ului<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Unul dintre cele mai periculoase comportamente ale Docker pe Linux este modul \u00een care interac\u021bioneaz\u0103 cu firewall-ul de sistem (iptables\/UFW). Implicit, Docker manipuleaz\u0103 regulile iptables pentru a permite traficul containerului. Asta \u00eenseamn\u0103 c\u0103, chiar dac\u0103 ai UFW activat \u0219i setat s\u0103 refuze tot traficul de intrare, publicarea unui port \u00een Docker (de exemplu, <code>-p 8080:80<\/code>) va ocoli adesea firewall-ul t\u0103u \u0219i va expune acel port \u00eentregului internet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Am v\u0103zut baze de date interne \u0219i panouri de administrare expuse accidental pe web-ul public deoarece administratorul a presupus c\u0103 UFW \u00eel protejeaz\u0103. Nu o f\u0103cea. Docker a f\u0103cut o gaur\u0103 direct prin el.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru a securiza acest lucru, leg\u0103m explicit porturile la interfa\u021ba localhost dac\u0103 nu sunt menite s\u0103 fie publice. \u00cen loc de <code>-p 8080:80<\/code>, folosim <code>-p 127.0.0.1:8080:80<\/code>. Acest lucru for\u021beaz\u0103 traficul s\u0103 treac\u0103 printr-un reverse proxy (ca Nginx) care ruleaz\u0103 pe gazd\u0103, ceea ce ne ofer\u0103 un punct central pentru terminarea SSL, controlul accesului \u0219i logging. Nu expunem niciodat\u0103 porturile containerului direct la internetul brut dec\u00e2t dac\u0103 este absolut necesar.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Monitorizarea s\u0103n\u0103t\u0103\u021bii containerului<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Un container care ruleaz\u0103 nu este neap\u0103rat un container s\u0103n\u0103tos. Un proces ar putea fi blocat \u00eentr-un deadlock, consum\u00e2nd zero CPU dar refuz\u00e2nd conexiuni. Statusul de baz\u0103 \u201eUp\u201d al Docker este insuficient pentru monitorizarea \u00een produc\u021bie. Folosim instruc\u021biunea <code>HEALTHCHECK<\/code> a Docker pentru a defini ce \u00eenseamn\u0103 de fapt \u201es\u0103n\u0103tos\u201d pentru fiecare serviciu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">De exemplu, un container de server web ar trebui considerat s\u0103n\u0103tos doar dac\u0103 returneaz\u0103 un r\u0103spuns 200 OK de la un endpoint specific, nu doar pentru c\u0103 PID-ul este activ. Integrarea acestor verific\u0103ri de s\u0103n\u0103tate ne permite s\u0103 configur\u0103m arhitecturi cu auto-vindecare, unde containerele nes\u0103n\u0103toase sunt automat oprite \u0219i \u00eenlocuite.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru clien\u021bii no\u0219tri, integr\u0103m metricile containerelor \u00een panoul nostru mai larg de monitorizare. Urm\u0103rim utilizarea CPU per container, presiunea memoriei \u0219i I\/O de re\u021bea. Aceast\u0103 vizibilitate granular\u0103 ne permite s\u0103 identific\u0103m un microserviciu specific care face probleme f\u0103r\u0103 a fi nevoie s\u0103 intr\u0103m prin SSH pe ma\u0219in\u0103 \u0219i s\u0103 rul\u0103m <code>htop<\/code> manual.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">C\u00e2nd s\u0103 externalizezi: baze de date \u00een containere vs. native<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Un subiect controversat \u00een lumea DevOps este dac\u0103 s\u0103 rulezi baze de date stateful (MySQL, PostgreSQL) \u00een interiorul containerelor. De\u0219i convenabil pentru dezvoltare, rularea bazelor de date mari \u00een Docker pe un VPS introduce overhead I\/O \u0219i complic\u0103 persisten\u021ba datelor. Dac\u0103 daemonul Docker se pr\u0103bu\u0219e\u0219te, baza ta de date se pr\u0103bu\u0219e\u0219te.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru \u00eenc\u0103rc\u0103rile de lucru de produc\u021bie unde integritatea datelor este primordial\u0103, recomand\u0103m adesea instalarea motorului de baze de date direct pe VPS-ul gazd\u0103 sau utilizarea unei solu\u021bii de baz\u0103 de date gestionate. Acest lucru elimin\u0103 stratul de abstractizare din calea I\/O, oferind o performan\u021b\u0103 mai bun\u0103 a discului \u0219i simplific\u00e2nd rutinile de backup. Dac\u0103 trebuie s\u0103 rulezi o baz\u0103 de date \u00eentr-un container, fixarea acesteia pe un director specific al gazdei prin bind mounts este nenegociabil\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Contextul de securitate \u0219i privilegiile utilizatorului<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Implicit, procesul din interiorul unui container Docker ruleaz\u0103 ca root. Dac\u0103 o vulnerabilitate permite unui atacator s\u0103 ias\u0103 din container (container escape), acesta ar putea poten\u021bial s\u0103 c\u00e2\u0219tige acces root la VPS-ul t\u0103u gazd\u0103. Acesta este un e\u0219ec de securitate catastrofal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ader\u0103m la principiul privilegiului minim. Ori de c\u00e2te ori este posibil, configur\u0103m containerele s\u0103 ruleze ca un utilizator non-root (UID 1000 sau similar). Acest lucru limiteaz\u0103 raza de impact a oric\u0103rei compromiteri de securitate. De asemenea, mont\u0103m sistemele de fi\u0219iere ca read-only oric\u00e2nd aplica\u021bia o suport\u0103, prevenind un atacator s\u0103 modifice codul aplica\u021biei chiar dac\u0103 reu\u0219e\u0219te s\u0103 intre.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Abordarea ServerSpan pentru containerele gestionate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Gestionarea acestei complexit\u0103\u021bi este un job cu norm\u0103 \u00eentreag\u0103. De aceea <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">serviciile gestionate<\/a> ServerSpan sunt concepute s\u0103 preia aceast\u0103 povar\u0103 de pe umerii t\u0103i. Nu doar \u201einstal\u0103m Docker\u201d \u0219i plec\u0103m. Arhitectur\u0103m mediul pentru stabilitate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Procesul nostru \u00eencepe cu o evaluare: Are aceast\u0103 aplica\u021bie nevoie de Docker? Dac\u0103 da, configur\u0103m daemonul cu set\u0103ri implicite sigure (rota\u021bie log-uri, live restore activat). Set\u0103m stivele <code>docker-compose<\/code> cu limite stricte de resurse \u0219i politici robuste de restart. Configur\u0103m firewall-ul pentru a ne asigura c\u0103 nu apare nicio expunere accidental\u0103. \u0218i, crucial, set\u0103m monitorizarea pentru a veghea la uciga\u0219ii t\u0103cu\u021bi precum epuizarea Inode-urilor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Construim infrastructura VPS subiacent\u0103 pentru a fi suficient de robust\u0103 pentru a gestiona overhead-ul, select\u00e2nd stocare NVMe \u0219i procesoare de \u00eenalt\u0103 frecven\u021b\u0103 care atenueaz\u0103 laten\u021ba introdus\u0103 de straturile de virtualizare. Fie c\u0103 rulezi o aplica\u021bie Dockerizat\u0103 simpl\u0103 sau un mesh complex de microservicii, scopul nostru este s\u0103 ne asigur\u0103m c\u0103 platforma de dedesubt r\u0103m\u00e2ne invizibil\u0103, stabil\u0103 \u0219i sigur\u0103.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Containerizarea a schimbat fundamental modul \u00een care sunt implementate aplica\u021biile, oferind promisiunea \u201ebuild once, run anywhere\u201d (construie\u0219te o dat\u0103, ruleaz\u0103 oriunde), care este incredibil de atractiv\u0103 pentru dezvoltatori. Totu\u0219i, realitatea opera\u021bional\u0103 a rul\u0103rii Docker pe un server privat virtual (VPS) este adesea mai pu\u021bin simpl\u0103 dec\u00e2t sugereaz\u0103 tutorialele. \u00cen experien\u021ba noastr\u0103 de gestionare a mii [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2389,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[14003,14014,14030,14022,13974,13989,14009,14010,14017,14015,14007,14004,14025,14001,14016,14021,14028,14000,14008,14023,14026,14027,14031,14005,14019,14024,14006,14013,14012,14002,14029,14018,14011,14020],"class_list":["post-2392","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-bune-practici-docker","tag-configurare-healthcheck-docker","tag-configurare-productie-docker","tag-docker-bind-mounts-vs-volume","tag-docker-oom-killer","tag-docker-system-prune","tag-docker-vs-nativ-performanta","tag-drivere-stocare-docker-overlay2","tag-epuizare-inode-docker","tag-gazduire-docker-gestionata","tag-gestionare-ciclu-viata-container","tag-gestionare-docker-pe-vps","tag-limite-cpu-docker","tag-limite-resurse-docker","tag-limite-resurse-docker-compose","tag-optimizare-docker-pentru-vps","tag-orchestrare-containere-vps","tag-performanta-docker-vps","tag-politici-restart-docker","tag-prevenire-prabusire-server-docker","tag-privilegii-utilizator-docker","tag-reparare-ocolire-ufw-docker","tag-riscuri-securitate-docker","tag-rotatie-log-uri-docker","tag-rulare-baze-de-date-in-docker","tag-scurgeri-memorie-container","tag-securitate-firewall-docker","tag-securitate-retea-docker","tag-securizare-containere-docker","tag-stabilitate-containere","tag-strategie-containerizare-vps","tag-suport-containere-serverspan","tag-unelte-monitorizare-docker","tag-versionare-imagini-docker"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2392","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2392"}],"version-history":[{"count":3,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2392\/revisions"}],"predecessor-version":[{"id":2396,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2392\/revisions\/2396"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2389"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2392"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2392"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2392"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}