{"id":1376,"date":"2024-07-23T12:39:19","date_gmt":"2024-07-23T12:39:19","guid":{"rendered":"https:\/\/dockerpros.com\/?post_type=glossary&p=1376"},"modified":"2024-07-23T12:39:19","modified_gmt":"2024-07-23T12:39:19","slug":"dockerfile-import-cache-key","status":"publish","type":"glossary","link":"https:\/\/dockerpros.com\/it\/wiki\/dockerfile-import-cache-key\/","title":{"rendered":"Dockerfile \u2013import-cache-key"},"content":{"rendered":"

Understanding Dockerfile \u2013import-cache-key: An Advanced Guide<\/h2>\n

The --import-cache-key<\/code> option in Dockerfile<\/a><\/span>Un Dockerfile \u00e8 uno script contenente una serie di istruzioni per automatizzare la creazione di immagini Docker. Specifica l'immagine di base, le dipendenze dell'applicazione e la configurazione, facilitando la distribuzione coerente in diversi ambienti. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> \u00e8 una funzionalit\u00e0 potente che migliora l'efficienza di immagine<\/a><\/span>An image is a visual representation of an object or scene, typically composed of pixels in digital formats. It can convey information, evoke emotions, and facilitate communication across various media. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> costruisce sfruttando i meccanismi di importazione della cache. Consente agli sviluppatori di specificare una chiave di cache per le immagini Docker, consentendo il riutilizzo degli strati memorizzati nella cache da immagini precedentemente costruite. Questa ottimizzazione non solo accelera il processo di costruzione, ma riduce anche la quantit\u00e0 di dati prelevati dai repository remoti, portando in ultima analisi a un miglioramento dei flussi di lavoro CI\/CD e dell'utilizzo delle risorse. Questo articolo approfondisce le complessit\u00e0 di --import-cache-key<\/code>, its use cases, and best practices for maximizing its benefits.<\/p>\n

L'Importanza della Memorizzazione nella Cache in Docker<\/h2>\n

Before diving into --import-cache-key<\/code>, it is essential to understand the concept of caching in Docker. When Docker builds an immagine<\/a><\/span>An image is a visual representation of an object or scene, typically composed of pixels in digital formats. It can convey information, evoke emotions, and facilitate communication across various media. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>, it goes through a series of steps, known as layers, each of which corresponds to a command in the Dockerfile<\/a><\/span>Un Dockerfile \u00e8 uno script contenente una serie di istruzioni per automatizzare la creazione di immagini Docker. Specifica l'immagine di base, le dipendenze dell'applicazione e la configurazione, facilitando la distribuzione coerente in diversi ambienti. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>. Docker caches the output of each command, so when the same command is executed again, Docker can skip the execution and reuse the cached result, significantly speeding up the build process.<\/p>\n

For instance, if a Dockerfile<\/a><\/span>Un Dockerfile \u00e8 uno script contenente una serie di istruzioni per automatizzare la creazione di immagini Docker. Specifica l'immagine di base, le dipendenze dell'applicazione e la configurazione, facilitando la distribuzione coerente in diversi ambienti. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> contains commands to install dependencies, Docker will cache those layers. If the dependencies have not changed, subsequent builds will reuse the cached layers instead of reinstalling them, saving time and resources. However, in complex CI\/CD pipelines or when dealing with large monorepos, determining the cache’s validity can become challenging, which is where --import-cache-key<\/code> comes into play.<\/p>\n

Che cos'\u00e8 --import-cache-key<\/code>?<\/h2>\n

The --import-cache-key<\/code> L'opzione \u00e8 stata introdotta in Docker 20.10 come parte della funzionalit\u00e0 BuildKit. Questa funzionalit\u00e0 consente agli utenti di specificare una chiave di cache per la cache importata, rendendo il processo di build pi\u00f9 prevedibile ed efficiente. Definendo una chiave di cache, gli utenti possono controllare quale cache viene utilizzata durante la build e come pu\u00f2 essere riutilizzata in diverse build.<\/p>\n

The syntax for using --import-cache-key<\/code> is as follows:<\/p>\n

docker build --importa-cache=TIPO=NOME --importa-cache-chiave=tua_chiave_cache .<\/code><\/pre>\n
Where TIPO<\/code> pu\u00f2 essere locale<\/code>, registry<\/a><\/span>A registry is a centralized database that stores information about various entities, such as software installations, system configurations, or user data. It serves as a crucial component for system management and configuration. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span><\/code>, o altri tipi di memorizzazione nella cache supportati da Docker. NAME<\/code> refers to the cache source (e.g., a local directory or a registry<\/a><\/span>A registry is a centralized database that stores information about various entities, such as software installations, system configurations, or user data. It serves as a crucial component for system management and configuration. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> immagine<\/a><\/span>An image is a visual representation of an object or scene, typically composed of pixels in digital formats. It can convey information, evoke emotions, and facilitate communication across various media. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>), e your_cache_key<\/code> is a string identifier that represents the cache state.<\/p>\n
Come --import-cache-key<\/code> Enhances Build Performance<\/h2>\n
Improved Cache Management<\/h3>\n
Introducendo --import-cache-key<\/code>, Docker provides developers with more granular control over caching behavior. This control allows teams to manage their build caches more effectively, especially in shared environments. By specifying cache keys, developers can ensure that builds are consistent and predictable, reducing the chances of unexpected changes due to stale caches.<\/p>\n
Differentiation Between Build Environments<\/h3>\n
In a CI\/CD setup, different environments may require different dependencies or configurations. The ability to set cache keys helps differentiate between these environments, allowing teams to define separate caches for each environment. For instance, a cache for development builds might include experimental features, while the cache for production builds might focus solely on stability. This separation ensures that changes in one environment do not inadvertently affect another.<\/p>\n
Cache Sharing Across Teams<\/h3>\n
In larger organizations, multiple teams may work on similar projects. With --import-cache-key<\/code>, teams can share cache across different builds, enhancing collaboration and reducing redundancy. For example, if one team builds a common library and pushes it to a shared registry<\/a><\/span>A registry is a centralized database that stores information about various entities, such as software installations, system configurations, or user data. It serves as a crucial component for system management and configuration. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>, other teams can import that cache using the defined key, minimizing duplicated work and improving overall efficiency.<\/p>\n
Casi d'uso pratici per --import-cache-key<\/code><\/h2>\n
Optimizing CI\/CD Pipelines<\/h3>\n
In a Continuous Integration\/Continuous Deployment (CI\/CD) pipeline, build times can become a bottleneck as more dependencies and services are added. Implementing --import-cache-key<\/code> allows for faster builds by reusing already built layers from previous builds. Teams can define cache keys that reflect the state of their dependencies, ensuring that only relevant caches are imported, leading to quicker and more efficient builds.<\/p>\n
Multistage Builds<\/h3>\n
Quando si utilizzano build a pi\u00f9 stadi, gli sviluppatori spesso desiderano ottimizzare come vengono costruite le loro immagini. Utilizzando --import-cache-key<\/code>, they can specify cache keys for intermediate stages, allowing for better performance and less redundant data. For instance, if the first stage of a build involves heavy immagine<\/a><\/span>An image is a visual representation of an object or scene, typically composed of pixels in digital formats. It can convey information, evoke emotions, and facilitate communication across various media. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> processing to compile assets, a cache key can be created for this stage. Subsequent builds can then use this key to import the cached data, thereby skipping the compilation step if the relevant files have not changed.<\/p>\n
Handling Dependency Updates<\/h3>\n
With frequent dependency updates, managing caches can become cumbersome. By employing --import-cache-key<\/code>, gli sviluppatori possono creare chiavi di cache che corrispondono a versioni specifiche delle dipendenze. Questa capacit\u00e0 consente di monitorare i cambiamenti in modo pi\u00f9 efficace. Quando una dipendenza viene aggiornata, i team possono modificare la chiave di cache, costringendo cos\u00ec il processo di build a rigenerare i livelli necessari, beneficiando comunque di altre cache invariate.<\/p>\n
Best Practices for Using --import-cache-key<\/code><\/h2>\n
Define Meaningful Cache Keys<\/h3>\n
When specifying cache keys, it is crucial to use meaningful names that reflect the state of the cache. This practice improves clarity when managing and debugging build processes. For example, using a cache key format like depends-v1.2.3<\/code>, che include la versione delle dipendenze, pu\u00f2 fornire indicazioni su quale cache viene utilizzata e aiutare a identificare i problemi pi\u00f9 rapidamente.<\/p>\n
Combina con altre funzionalit\u00e0 di BuildKit<\/h3>\n
Il vero potere di --import-cache-key<\/code> becomes apparent when combined with other BuildKit features such as --cache-from<\/code> and --target<\/code>. Sfruttando le multiple opzioni di caching, gli sviluppatori possono creare processi di compilazione robusti che massimizzano l'efficienza e minimizzano la ridondanza. Ad esempio, utilizzando. --cache-from<\/code> allows for pulling cache from a registry<\/a><\/span>A registry is a centralized database that stores information about various entities, such as software installations, system configurations, or user data. It serves as a crucial component for system management and configuration. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>, while --import-cache-key<\/code> Mantiene le chiavi della cache locale, offrendo flessibilit\u00e0 su come e dove le cache vengono gestite.<\/p>\n
Monitor Cache Usage<\/h3>\n
Il monitoraggio dell'utilizzo della cache \u00e8 essenziale per ottimizzare le prestazioni di compilazione. Tenere traccia delle cache utilizzate frequentemente e di quelle non utilizzate pu\u00f2 fornire informazioni su se le cache devono essere aggiornate o rimosse. Strumenti come i log di output di Docker possono aiutare gli sviluppatori a identificare i colpi e i mancati colpi della cache, consentendo una migliore gestione delle decisioni relative alla gestione della cache.<\/p>\n
Aggiorna regolarmente le chiavi della cache<\/h3>\n
As projects evolve, so do their dependencies. Regularly updating cache keys in accordance with dependency changes ensures that caches remain relevant. This practice helps avoid stale caches that could lead to inconsistent builds. Additionally, it can help in identifying potential security vulnerabilities that may arise from outdated dependencies.<\/p>\n
Common Challenges with --import-cache-key<\/code><\/h2>\n
Complessit\u00e0 nella gestione della cache<\/h3>\n
Mentre --import-cache-key<\/code> offre un controllo migliorato sul comportamento della cache, ma introduce anche complessit\u00e0. Man mano che vengono definiti pi\u00f9 chiavi di cache, pu\u00f2 diventare difficile tenerne traccia e gestirle efficacemente. I team dovrebbero implementare documentazione e revisioni regolari delle strategie di cache per mitigare questa complessit\u00e0.<\/p>\n
Performance Overheads<\/h3>\n
In alcuni casi, chiavi di cache configurate in modo improprio possono causare sovraccarichi di prestazioni. Se le chiavi di cache sono troppo granulari, Docker potrebbe impiegare pi\u00f9 tempo a gestire le cache che a costruire effettivamente. Trovare il giusto equilibrio tra specificit\u00e0 e semplicit\u00e0 delle chiavi di cache \u00e8 essenziale per mantenere build efficienti.<\/p>\n
Incompatibility with Legacy Builds<\/h3>\n
Le versioni precedenti di Docker potrebbero non supportare --import-cache-key<\/code>, portando a sfide di compatibilit\u00e0 in ambienti misti. I team dovrebbero assicurarsi che tutti gli sviluppatori e i sistemi CI\/CD utilizzino versioni di Docker compatibili per sfruttare appieno questa funzionalit\u00e0.<\/p>\n
Conclusione<\/h2>\n
The --import-cache-key<\/code> option in Dockerfile<\/a><\/span>Un Dockerfile \u00e8 uno script contenente una serie di istruzioni per automatizzare la creazione di immagini Docker. Specifica l'immagine di base, le dipendenze dell'applicazione e la configurazione, facilitando la distribuzione coerente in diversi ambienti. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> is a significant enhancement to Docker’s caching capabilities, allowing for more efficient immagine<\/a><\/span>An image is a visual representation of an object or scene, typically composed of pixels in digital formats. It can convey information, evoke emotions, and facilitate communication across various media. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> builds and better resource management. By providing developers with greater control over their caching strategies, this feature can significantly improve CI\/CD workflows, reduce build times, and facilitate collaboration across teams.<\/p>\n
As teams adopt --import-cache-key<\/code>, dovrebbero rimanere consapevoli delle migliori pratiche, come la definizione di chiavi di cache significative, il monitoraggio dell'utilizzo della cache e l'aggiornamento regolare di tali chiavi per riflettere i cambiamenti nelle dipendenze. Sebbene esistano sfide, i vantaggi dell'utilizzo --import-cache-key<\/code> superano di gran lunga le complessit\u00e0 coinvolte.<\/p>\n
In a world where speed and efficiency are paramount, leveraging advanced Docker features like --import-cache-key<\/code> pu\u00f2 portare a guadagni sostanziali in termini di produttivit\u00e0 e risultati del progetto. Mentre incorpori questo potente strumento nei tuoi flussi di lavoro Docker, ricorda che una gestione efficace della cache \u00e8 fondamentale per sfruttare appieno il suo potenziale, aprendo la strada a build pi\u00f9 fluide e veloci nelle tue attivit\u00e0 di sviluppo.<\/p>","protected":false},"excerpt":{"rendered":"
The `\u2013import-cache-key` option in Dockerfile<\/a><\/span>Un Dockerfile \u00e8 uno script contenente una serie di istruzioni per automatizzare la creazione di immagini Docker. Specifica l'immagine di base, le dipendenze dell'applicazione e la configurazione, facilitando la distribuzione coerente in diversi ambienti. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> allows users to specify a cache key for imported cache layers, optimizing immagine<\/a><\/span>An image is a visual representation of an object or scene, typically composed of pixels in digital formats. It can convey information, evoke emotions, and facilitate communication across various media. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> costruisce. Questa funzionalit\u00e0 migliora l'efficienza della build riutilizzando i livelli esistenti in base alle chiavi definite.<\/p>","protected":false},"author":1,"featured_media":2065,"parent":0,"template":"","glossary-cat":[],"class_list":["post-1376","glossary","type-glossary","status-publish","has-post-thumbnail","hentry"],"yoast_head":"\nDockerfile -import-cache-key - Dockerpros<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dockerpros.com\/it\/wiki\/dockerfile-import-cache-key\/\" \/>\n<meta property=\"og:locale\" content=\"it_IT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Dockerfile -import-cache-key - Dockerpros\" \/>\n<meta property=\"og:description\" content=\"The `--import-cache-key` option in Dockerfile allows users to specify a cache key for imported cache layers, optimizing image builds. This feature enhances build efficiency by reusing existing layers based on defined keys.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dockerpros.com\/it\/wiki\/dockerfile-import-cache-key\/\" \/>\n<meta property=\"og:site_name\" content=\"Dockerpros\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-import-cache-key_1376.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"800\" \/>\n\t<meta property=\"og:image:height\" content=\"600\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo di lettura stimato\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minuti\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/\",\"url\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/\",\"name\":\"Dockerfile -import-cache-key - Dockerpros\",\"isPartOf\":{\"@id\":\"https:\/\/dockerpros.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-import-cache-key_1376.jpg\",\"datePublished\":\"2024-07-23T12:39:19+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#breadcrumb\"},\"inLanguage\":\"it-IT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#primaryimage\",\"url\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-import-cache-key_1376.jpg\",\"contentUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-import-cache-key_1376.jpg\",\"width\":800,\"height\":600,\"caption\":\"dockerfile-import-cache-key-2\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dockerpros.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Glossary\",\"item\":\"https:\/\/dockerpros.com\/fr\/wiki\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Dockerfile –import-cache-key\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dockerpros.com\/#website\",\"url\":\"https:\/\/dockerpros.com\/\",\"name\":\"Dockerpros\",\"description\":\"DockerPros \u2013 Your Ultimate Docker Resource Hub\",\"publisher\":{\"@id\":\"https:\/\/dockerpros.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dockerpros.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"it-IT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dockerpros.com\/#organization\",\"name\":\"Dockerpros\",\"url\":\"https:\/\/dockerpros.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/dockerpros.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/Dockerpros_logo_blanco.png\",\"contentUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/Dockerpros_logo_blanco.png\",\"width\":532,\"height\":114,\"caption\":\"Dockerpros\"},\"image\":{\"@id\":\"https:\/\/dockerpros.com\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Dockerfile -import-cache-key - esperti Docker","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/dockerpros.com\/it\/wiki\/dockerfile-import-cache-key\/","og_locale":"it_IT","og_type":"article","og_title":"Dockerfile -import-cache-key - Dockerpros","og_description":"The `--import-cache-key` option in Dockerfile allows users to specify a cache key for imported cache layers, optimizing image builds. This feature enhances build efficiency by reusing existing layers based on defined keys.","og_url":"https:\/\/dockerpros.com\/it\/wiki\/dockerfile-import-cache-key\/","og_site_name":"Dockerpros","og_image":[{"width":800,"height":600,"url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-import-cache-key_1376.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Tempo di lettura stimato":"6 minuti"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/","url":"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/","name":"Dockerfile -import-cache-key - esperti Docker","isPartOf":{"@id":"https:\/\/dockerpros.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#primaryimage"},"image":{"@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#primaryimage"},"thumbnailUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-import-cache-key_1376.jpg","datePublished":"2024-07-23T12:39:19+00:00","breadcrumb":{"@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#breadcrumb"},"inLanguage":"it-IT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/"]}]},{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#primaryimage","url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-import-cache-key_1376.jpg","contentUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-import-cache-key_1376.jpg","width":800,"height":600,"caption":"dockerfile-import-cache-key-2"},{"@type":"BreadcrumbList","@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-import-cache-key\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dockerpros.com\/"},{"@type":"ListItem","position":2,"name":"Glossary","item":"https:\/\/dockerpros.com\/fr\/wiki\/"},{"@type":"ListItem","position":3,"name":"Dockerfile –import-cache-key"}]},{"@type":"WebSite","@id":"https:\/\/dockerpros.com\/#website","url":"https:\/\/dockerpros.com\/","name":"Esperti Docker","description":"DockerPros \u2013 Il tuo punto di riferimento definitivo per Docker","publisher":{"@id":"https:\/\/dockerpros.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dockerpros.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"it-IT"},{"@type":"Organization","@id":"https:\/\/dockerpros.com\/#organization","name":"Esperti Docker","url":"https:\/\/dockerpros.com\/","logo":{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/dockerpros.com\/#\/schema\/logo\/image\/","url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/Dockerpros_logo_blanco.png","contentUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/Dockerpros_logo_blanco.png","width":532,"height":114,"caption":"Dockerpros"},"image":{"@id":"https:\/\/dockerpros.com\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/glossary\/1376","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/types\/glossary"}],"author":[{"embeddable":true,"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/glossary\/1376\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/media\/2065"}],"wp:attachment":[{"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/media?parent=1376"}],"wp:term":[{"taxonomy":"glossary-cat","embeddable":true,"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/glossary-cat?post=1376"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}