{"id":476411,"date":"2023-08-09T07:29:55","date_gmt":"2023-08-09T07:29:55","guid":{"rendered":""},"modified":"2023-09-05T11:12:42","modified_gmt":"2023-09-05T11:12:42","slug":"container-isolation","status":"publish","type":"wiki","link":"https:\/\/oneproxy.pro\/tr\/wiki\/container-isolation\/","title":{"rendered":"Konteyner izolasyonu"},"content":{"rendered":"<p>Konteyner izolasyonu, bireysel konteynerlerin birbirinden ve ana sistemden ayr\u0131ld\u0131\u011f\u0131 ve izole edildi\u011fi mekanizmay\u0131 ifade eder. Konteynerlerin izolasyonu, yaz\u0131l\u0131m uygulamalar\u0131n\u0131n ve temel sistem ortam\u0131n\u0131n g\u00fcvenli\u011fini ve b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc sa\u011flamak a\u00e7\u0131s\u0131ndan \u00e7ok \u00f6nemlidir.<\/p>\n<h2>Konteyner \u0130zolasyonunun Geli\u015fimi ve \u0130lk S\u00f6zleri<\/h2>\n<p>Konteyner izolasyonu fikri, i\u015fletim sistemlerinde proses izolasyonunun gereklili\u011finden do\u011fmu\u015ftur. 1982 y\u0131l\u0131nda Unix benzeri sistemler i\u00e7in geli\u015ftirilen Chroot, konteynerle\u015ftirmeye y\u00f6nelik ilk b\u00fcy\u00fck ad\u0131md\u0131 ancak s\u0131n\u0131rl\u0131 bir izolasyon sunuyordu.<\/p>\n<p>Modern konteyner izolasyonu kavram\u0131, 2000&#039;li y\u0131llar\u0131n ba\u015f\u0131nda FreeBSD hapishanelerinin ve Solaris B\u00f6lgelerinin piyasaya s\u00fcr\u00fclmesiyle ortaya \u00e7\u0131kt\u0131. Ancak 2008&#039;de Linux Konteynerlerinin (LXC) piyasaya s\u00fcr\u00fclmesinden sonra konteynerle\u015ftirme \u00f6nemli bir ivme kazanmaya ba\u015flad\u0131. LXC, tek bir Linux ana bilgisayar\u0131nda birden fazla yal\u0131t\u0131lm\u0131\u015f Linux sistemini (konteyner) \u00e7al\u0131\u015ft\u0131rabilen sanal bir ortam olu\u015fturmak \u00fczere tasarlanm\u0131\u015ft\u0131r.<\/p>\n<p>&quot;Konteyner \u0130zolasyonu&quot; terimi, 2013 y\u0131l\u0131nda Docker&#039;\u0131n ortaya \u00e7\u0131k\u0131\u015f\u0131yla ilgi oda\u011f\u0131 haline geldi. Docker, LXC&#039;yi kendi k\u00fct\u00fcphanesi olan libcontainer ile de\u011fi\u015ftirmeden \u00f6nce ilk a\u015famalar\u0131nda kulland\u0131.<\/p>\n<h2>Konteyner \u0130zolasyonunun Derinli\u011fine Dal\u0131\u015f<\/h2>\n<p>Container izolasyonu tamamen uygulamalar\u0131n birbirine m\u00fcdahale etmeden \u00e7al\u0131\u015fabilece\u011fi ba\u011f\u0131ms\u0131z alanlar yaratmakla ilgilidir. Ad alanlar\u0131, gruplar (kontrol gruplar\u0131) ve katmanl\u0131 dosya sistemleri dahil olmak \u00fczere \u00e7e\u015fitli teknikleri ve Linux \u00e7ekirdek \u00f6zelliklerini kullan\u0131r.<\/p>\n<ol>\n<li>\n<p><strong>Ad alanlar\u0131:<\/strong> Ad alanlar\u0131, bir i\u015flemin g\u00f6rebileceklerini k\u0131s\u0131tlayarak, i\u015flemin i\u015fletim sistemi ortam\u0131na bak\u0131\u015f\u0131n\u0131 izole eder. Farkl\u0131 ad alanlar\u0131 t\u00fcrleri aras\u0131nda \u0130\u015flem Kimli\u011fi (PID) ad alanlar\u0131, a\u011f ad alanlar\u0131, ba\u011flama ad alanlar\u0131 ve kullan\u0131c\u0131 ad alanlar\u0131 bulunur.<\/p>\n<\/li>\n<li>\n<p><strong>Gruplar:<\/strong> Kontrol Gruplar\u0131 bir i\u015flemin kullanabilece\u011fi \u015feyleri (\u00f6rne\u011fin CPU, bellek, a\u011f bant geni\u015fli\u011fi vb.) s\u0131n\u0131rlar. Ayr\u0131ca kaynak kullan\u0131m\u0131n\u0131n \u00f6nceliklendirilmesine ve hesaplanmas\u0131na da yard\u0131mc\u0131 olurlar.<\/p>\n<\/li>\n<li>\n<p><strong>Katmanl\u0131 Dosya Sistemleri:<\/strong> Bunlar, g\u00f6r\u00fcnt\u00fc katmanlar\u0131n\u0131n ayr\u0131lmas\u0131n\u0131 ve \u00fcst \u00fcste bindirilmesini sa\u011flar ve Docker g\u00f6r\u00fcnt\u00fclerini ve kapsay\u0131c\u0131lar\u0131n\u0131 y\u00f6netmek i\u00e7in kritik \u00f6neme sahiptir.<\/p>\n<\/li>\n<\/ol>\n<h2>Konteyner \u0130zolasyonunun \u0130\u00e7 Yap\u0131s\u0131 ve Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/h2>\n<p>Mimari a\u00e7\u0131dan konteyner izolasyonu a\u015fa\u011f\u0131daki bile\u015fenler kullan\u0131larak sa\u011flan\u0131r:<\/p>\n<ol>\n<li>\n<p><strong>Konteyner \u00c7al\u0131\u015fma S\u00fcresi:<\/strong> Bu, Docker, Containerd veya CRI-O gibi konteynerleri \u00e7al\u0131\u015ft\u0131ran ve y\u00f6neten yaz\u0131l\u0131md\u0131r.<\/p>\n<\/li>\n<li>\n<p><strong>Konteyner G\u00f6rselleri:<\/strong> Bunlar, bir yaz\u0131l\u0131m\u0131 \u00e7al\u0131\u015ft\u0131rmak i\u00e7in gereken her \u015feyi i\u00e7eren hafif, ba\u011f\u0131ms\u0131z, y\u00fcr\u00fct\u00fclebilir paketlerdir.<\/p>\n<\/li>\n<li>\n<p><strong>Konteyner Motoru:<\/strong> Bu, kapsay\u0131c\u0131lar olu\u015fturmak i\u00e7in ana sistemin \u00e7ekirde\u011fini kullanan temel yaz\u0131l\u0131md\u0131r.<\/p>\n<\/li>\n<\/ol>\n<p>Konteyner izolasyonunun i\u015f ak\u0131\u015f\u0131 a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 i\u00e7erir:<\/p>\n<ol>\n<li>Kapsay\u0131c\u0131 \u00e7al\u0131\u015fma zaman\u0131 gerekli kapsay\u0131c\u0131 g\u00f6r\u00fcnt\u00fcs\u00fcn\u00fc \u00e7eker.<\/li>\n<li>G\u00f6r\u00fcnt\u00fc konteyner motoruna y\u00fcklenir.<\/li>\n<li>Konteyner motoru, ad alanlar\u0131n\u0131, gruplar\u0131 ve g\u00f6r\u00fcnt\u00fcn\u00fcn dosya sistemini kullanarak yal\u0131t\u0131lm\u0131\u015f bir ortam olu\u015fturur.<\/li>\n<li>Konteyner i\u00e7indeki uygulama daha sonra di\u011fer konteynerlerden ve ana bilgisayar sisteminden izole edilerek y\u00fcr\u00fct\u00fcl\u00fcr.<\/li>\n<\/ol>\n<h2>Konteyner \u0130zolasyonunun Temel \u00d6zellikleri<\/h2>\n<ul>\n<li><strong>G\u00fcvenlik:<\/strong> Konteynerler birbirlerinden izole edilmi\u015ftir; bu, bir konteynerdeki bir g\u00fcvenlik a\u00e7\u0131\u011f\u0131n\u0131n veya hatan\u0131n di\u011ferlerini etkilemesini engeller.<\/li>\n<li><strong>Kaynak Kontrol\u00fc:<\/strong> Cgroup&#039;lar arac\u0131l\u0131\u011f\u0131yla, konteynerler sistem kaynaklar\u0131n\u0131n kontroll\u00fc bir pay\u0131na sahip olur ve bu da herhangi bir konteynerin kaynaklar\u0131 tekeline almas\u0131n\u0131 engeller.<\/li>\n<li><strong>Ta\u015f\u0131nabilirlik:<\/strong> Konteyner yal\u0131t\u0131m\u0131, uygulamay\u0131 ve ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 tek bir birimde kaps\u00fclleyerek yaz\u0131l\u0131m\u0131n farkl\u0131 ortamlarda tutarl\u0131 bir \u015fekilde \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar.<\/li>\n<li><strong>Yeterlik:<\/strong> Konteynerler, ana bilgisayar\u0131n \u00e7ekirde\u011fini payla\u015ft\u0131klar\u0131ndan hafiftir ve geleneksel VM&#039;lerden \u00e7ok daha h\u0131zl\u0131 ba\u015flat\u0131l\u0131r.<\/li>\n<\/ul>\n<h2>Konteyner \u0130zolasyon \u00c7e\u015fitleri<\/h2>\n<p>Konteyner izolasyonunun temel fikri ayn\u0131 kalsa da izolasyonu \u00e7e\u015fitli \u015fekillerde sa\u011flayacak \u015fekilde farkl\u0131 platformlar geli\u015fti. A\u015fa\u011f\u0131daki tabloda baz\u0131 \u00f6nemli konteyner platformlar\u0131 ve bunlar\u0131n benzersiz y\u00f6nleri \u00f6zetlenmektedir:<\/p>\n<table>\n<thead>\n<tr>\n<th>Konteyner Platformu<\/th>\n<th>Tan\u0131m<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Liman i\u015f\u00e7isi<\/td>\n<td>\u0130\u015flemleri yal\u0131t\u0131lm\u0131\u015f olarak \u00e7al\u0131\u015ft\u0131ran hafif kapsay\u0131c\u0131lar sa\u011flamak i\u00e7in \u00fcst d\u00fczey bir API sa\u011flar.<\/td>\n<\/tr>\n<tr>\n<td>LXC (Linux Konteynerleri)<\/td>\n<td>Ayr\u0131 bir \u00e7ekirde\u011fe ihtiya\u00e7 duymadan standart Linux kurulumuna m\u00fcmk\u00fcn oldu\u011funca yak\u0131n bir ortam sunar.<\/td>\n<\/tr>\n<tr>\n<td>Rkt (Roket)<\/td>\n<td>G\u00fcvenlik, basitlik ve \u015fekillendirilebilirlik odakl\u0131 sunucu ortamlar\u0131 i\u00e7in tasarlanm\u0131\u015ft\u0131r.<\/td>\n<\/tr>\n<tr>\n<td>Konteynerli<\/td>\n<td>Depolama, g\u00f6r\u00fcnt\u00fc da\u011f\u0131t\u0131m\u0131 ve a\u011f aray\u00fczleri de dahil olmak \u00fczere konteyner ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fcn tamam\u0131n\u0131 y\u00f6neten \u00fcst d\u00fczey bir konteyner \u00e7al\u0131\u015fma zaman\u0131.<\/td>\n<\/tr>\n<tr>\n<td>CRI-O<\/td>\n<td>\u00c7\u0131plak donan\u0131m uygulamalar\u0131n\u0131n h\u0131z\u0131 ile mikroVM soyutlamas\u0131 aras\u0131nda bir denge sunan, \u00f6zellikle Kubernetes&#039;e y\u00f6nelik hafif bir konteyner \u00e7al\u0131\u015fma zaman\u0131.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Konteyner Yal\u0131t\u0131m\u0131n\u0131 Kullanma: Sorunlar ve \u00c7\u00f6z\u00fcmler<\/h2>\n<p>Konteyner izolasyonu, s\u00fcrekli entegrasyon\/s\u00fcrekli teslimat (CI\/CD), mikro hizmet mimarisi ve bulutta yerel uygulamalar dahil olmak \u00fczere yaz\u0131l\u0131m geli\u015ftirme ve da\u011f\u0131t\u0131m\u0131nda \u00e7ok say\u0131da amaca hizmet eder.<\/p>\n<p>Ancak a\u015fa\u011f\u0131daki gibi zorluklar ortaya \u00e7\u0131kabilir:<\/p>\n<ol>\n<li><strong>G\u00fcvenlik endi\u015feleri:<\/strong> \u0130zolasyona ra\u011fmen konteynerler ana bilgisayar\u0131n \u00e7ekirde\u011fini payla\u015f\u0131yor ve bu da onu potansiyel bir sald\u0131r\u0131 y\u00fczeyi haline getiriyor. \u00c7\u00f6z\u00fcmler aras\u0131nda d\u00fczenli g\u00fcncellemeler ve yamalar ile Seccomp, AppArmor veya SELinux gibi ek g\u00fcvenlik ara\u00e7lar\u0131n\u0131n kullan\u0131lmas\u0131 yer al\u0131r.<\/li>\n<li><strong>Performans Ek Y\u00fck\u00fc:<\/strong> \u00c7ok fazla kapsay\u0131c\u0131 sistem kayna\u011f\u0131 \u00e7eki\u015fmesine neden olabilir. Verimli kaynak y\u00f6netimi ve y\u00fck dengeleme bu sorunun hafifletilmesine yard\u0131mc\u0131 olabilir.<\/li>\n<li><strong>Karma\u015f\u0131kl\u0131k:<\/strong> \u00d6zellikle mikro hizmet mimarisinde bir\u00e7ok kapsay\u0131c\u0131y\u0131 y\u00f6netmek karma\u015f\u0131k olabilir. Kubernetes veya Docker Swarm gibi konteyner d\u00fczenleme ara\u00e7lar\u0131 bu karma\u015f\u0131kl\u0131\u011f\u0131 y\u00f6netebilir.<\/li>\n<\/ol>\n<h2>Konteyner \u0130zolasyonunu Benzer Terimlerle Kar\u015f\u0131la\u015ft\u0131rma<\/h2>\n<p>Her ne kadar her ikisi de uygulamalar\u0131n \u00e7al\u0131\u015fmas\u0131 i\u00e7in yal\u0131t\u0131lm\u0131\u015f ortamlar sa\u011flasa da, konteyner izolasyonu sanalla\u015ft\u0131rmayla kar\u0131\u015ft\u0131r\u0131lmamal\u0131d\u0131r.<\/p>\n<ul>\n<li><strong>Sanal Makineler (VM&#039;ler)<\/strong>: VM&#039;ler, her biri kendi i\u015fletim sistemine sahip olan eksiksiz bir ana bilgisayar\u0131n taklit edilmesine dayan\u0131r. VM&#039;ler konteynerlere k\u0131yasla daha a\u011f\u0131rd\u0131r ve \u00f6ny\u00fckleme s\u00fcreleri daha uzundur.<\/li>\n<li><strong>Konteynerler<\/strong>: Konteynerler, ana bilgisayar\u0131n i\u015fletim sistemi \u00e7ekirde\u011fini payla\u015farak onlar\u0131 daha hafif ve daha h\u0131zl\u0131 ba\u015flat\u0131l\u0131r hale getirir. VM&#039;lerde oldu\u011fu gibi sistem d\u00fczeyinde izolasyon yerine s\u00fcre\u00e7 seviyesinde izolasyon sa\u011flarlar.<\/li>\n<\/ul>\n<h2>Konteyner \u0130zolasyonunda Gelecek Perspektifleri ve Teknolojiler<\/h2>\n<p>Gelece\u011fe bak\u0131ld\u0131\u011f\u0131nda konteyner izolasyon teknolojisinin \u00f6zellikle g\u00fcvenlik a\u00e7\u0131s\u0131ndan geli\u015fmesi bekleniyor. WebAssembly (Wasm) ve eBPF&#039;nin (geni\u015fletilmi\u015f Berkeley Paket Filtresi) benimsenmesiyle daha k\u00fc\u00e7\u00fck, daha h\u0131zl\u0131 ve daha g\u00fcvenli yeni nesil konteynerler g\u00f6rebiliriz.<\/p>\n<p>MikroVM kavram\u0131 da dikkat \u00e7ekiyor. Firecracker gibi MicroVM&#039;ler, geleneksel VM&#039;lerin g\u00fcvenlik avantajlar\u0131n\u0131 ve konteynerlerin kaynak verimlili\u011fini sa\u011flayarak onlar\u0131 \u00e7ok kirac\u0131l\u0131 ortamlar i\u00e7in ideal hale getirir.<\/p>\n<h2>Proxy Sunucular\u0131 ve Konteyner Yal\u0131t\u0131m\u0131<\/h2>\n<p>Proxy sunucular\u0131 konteyner yal\u0131t\u0131m\u0131ndan \u00f6nemli \u00f6l\u00e7\u00fcde yararlanabilir. OneProxy gibi proxy sa\u011flay\u0131c\u0131lar\u0131 birden fazla m\u00fc\u015fterinin verilerini i\u015fledi\u011finden, kapsay\u0131c\u0131 izolasyonu her m\u00fc\u015fterinin i\u015flemlerini ay\u0131rmaya yard\u0131mc\u0131 olabilir. Bu, bir m\u00fc\u015fterinin etkinlikleri tehlikeye girse bile di\u011ferlerinin etkilenmemesi nedeniyle g\u00fcvenli\u011fi art\u0131r\u0131r.<\/p>\n<p>Proxy sa\u011flay\u0131c\u0131lar\u0131, konteyner d\u00fczenleme platformlar\u0131n\u0131 kullanarak, konteyner olarak konu\u015fland\u0131r\u0131lan binlerce proxy sunucusunun ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc verimli bir \u015fekilde y\u00f6netebilir. Bu yakla\u015f\u0131m \u00f6l\u00e7eklenebilirli\u011fi, s\u00fcrd\u00fcr\u00fclebilirli\u011fi ve hata tolerans\u0131n\u0131 art\u0131r\u0131r.<\/p>\n<h2>\u0130lgili Ba\u011flant\u0131lar<\/h2>\n<p>Konteyner \u0130zolasyonu hakk\u0131nda daha fazla bilgi i\u00e7in a\u015fa\u011f\u0131daki kaynaklara bak\u0131n:<\/p>\n<ol>\n<li><a href=\"https:\/\/docs.docker.com\/compose\/\" target=\"_new\" rel=\"noopener nofollow\">Docker: Docker Compose&#039;a Genel Bak\u0131\u015f<\/a><\/li>\n<li><a href=\"https:\/\/kubernetes.io\/what-is-kubernetes\/\" target=\"_new\" rel=\"noopener nofollow\">Kubernetes: Kubernetes nedir?<\/a><\/li>\n<li><a href=\"https:\/\/linuxcontainers.org\/lxc\/introduction\/\" target=\"_new\" rel=\"noopener nofollow\">LXC: Linux Konteynerleri<\/a><\/li>\n<li><a href=\"https:\/\/cri-o.io\/\" target=\"_new\" rel=\"noopener nofollow\">CRI-O: Kubernetes i\u00e7in Hafif Konteyner \u00c7al\u0131\u015fma Zaman\u0131<\/a><\/li>\n<li><a href=\"https:\/\/firecracker-microvm.github.io\/\" target=\"_new\" rel=\"noopener nofollow\">Firecracker: Sunucusuz Bilgi \u0130\u015flem i\u00e7in G\u00fcvenli ve H\u0131zl\u0131 microVM&#039;ler<\/a><\/li>\n<\/ol>\n<p>Konteyner yal\u0131t\u0131m\u0131, mevcut bulut tabanl\u0131 uygulama dalgas\u0131n\u0131n merkezinde yer al\u0131r ve sa\u011flam, \u00f6l\u00e7eklenebilir ve g\u00fcvenli uygulama da\u011f\u0131t\u0131m\u0131 vaadi sunar. Teknoloji end\u00fcstrisindeki, \u00f6zellikle proxy sunucu sa\u011flay\u0131c\u0131lar\u0131 gibi sekt\u00f6rlerdeki \u00f6nemi artmaya devam edecek.<\/p>","protected":false},"featured_media":476412,"menu_order":0,"template":"","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"class_list":["post-476411","wiki","type-wiki","status-publish","has-post-thumbnail","hentry"],"acf":{"faq_title":"Frequently Asked Questions about <mark>Container Isolation: A Comprehensive Analysis<\/mark>","faq_items":[{"question":"What is Container Isolation?","answer":"<p>Container Isolation refers to the method by which individual containers are kept separate from each other and the host system. This isolation is crucial in ensuring the security and integrity of both software applications and the underlying system environment.<\/p>"},{"question":"When did the concept of Container Isolation emerge?","answer":"<p>The concept of container isolation originated from the necessity for process isolation in operating systems, with the first step towards containerization being Chroot, developed in 1982 for Unix-like systems. Modern container isolation, as we know it today, started gaining significant attention with the introduction of Linux Containers (LXC) in 2008 and later with Docker in 2013.<\/p>"},{"question":"How does Container Isolation work?","answer":"<p>Container isolation creates independent spaces where applications can run without interfering with each other or the host system. It employs several techniques and Linux kernel features, including namespaces, control groups (cgroups), and layered file systems.<\/p>"},{"question":"What are the key features of Container Isolation?","answer":"<p>Container Isolation is characterized by several key features such as security, resource control, portability, and efficiency. The isolation between containers enhances security, while resource control ensures no single container monopolizes system resources. The encapsulation of an application and its dependencies into a single unit provides portability, and the lightweight nature of containers enhances efficiency.<\/p>"},{"question":"What are some types of Container Isolation?","answer":"<p>Different platforms have evolved to provide isolation in various ways, some of which include Docker, Linux Containers (LXC), Rocket (Rkt), Containerd, and CRI-O.<\/p>"},{"question":"What are some common issues with Container Isolation and their solutions?","answer":"<p>Some challenges associated with Container Isolation include security concerns, performance overhead, and management complexity. Solutions include regular system updates, patches, using additional security tools, efficient resource management, load balancing, and container orchestration tools.<\/p>"},{"question":"How does Container Isolation compare to similar concepts like Virtual Machines?","answer":"<p>Unlike virtual machines (VMs) that emulate a complete host with its own operating system, containers provide process-level isolation and share the host's OS kernel. This makes containers lightweight and faster to boot compared to VMs.<\/p>"},{"question":"How is Container Isolation expected to evolve in the future?","answer":"<p>Container Isolation technology is expected to improve further, especially in the area of security. Future trends point towards the adoption of WebAssembly (Wasm), eBPF (extended Berkeley Packet Filter), and the concept of microVMs like Firecracker that combine the security advantages of traditional VMs and the resource efficiency of containers.<\/p>"},{"question":"What is the relationship between Proxy Servers and Container Isolation?","answer":"<p>In the context of proxy servers, container isolation can segregate each client's operations, thereby enhancing security. Container orchestration platforms also enable proxy providers to manage thousands of proxy servers deployed as containers effectively, improving scalability, maintainability, and fault tolerance.<\/p>"}]},"_links":{"self":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki\/476411","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki"}],"about":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/types\/wiki"}],"version-history":[{"count":0,"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki\/476411\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media\/476412"}],"wp:attachment":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media?parent=476411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}