{"id":1390,"date":"2024-07-23T12:39:25","date_gmt":"2024-07-23T12:39:25","guid":{"rendered":"https:\/\/dockerpros.com\/?post_type=glossary&p=1390"},"modified":"2024-07-23T12:39:25","modified_gmt":"2024-07-23T12:39:25","slug":"sovraccarico-della-cache-del-dockerfile","status":"publish","type":"glossary","link":"https:\/\/dockerpros.com\/it\/wiki\/dockerfile-cache-overhead\/","title":{"rendered":"Dockerfile \u2013cache-overhead"},"content":{"rendered":"

Understanding Dockerfile \u2013cache-overhead: An In-Depth Analysis<\/h1>\n

Nel mondo della containerizzazione, Docker \u00e8 emerso come soluzione leader per costruire, distribuire e gestire applicazioni in ambienti leggeri. Una delle funzionalit\u00e0 critiche di Docker \u00e8 la sua capacit\u00e0 di memorizzare nella cache i livelli delle immagini per ottimizzare i tempi di build. Tuttavia, il --cache-overhead<\/code> flag introduces a nuanced consideration of this caching mechanism, allowing developers to better control their build times and resource utilization. This article aims to provide a comprehensive analysis of Dockerfile\u2019s --cache-overhead<\/code>, le sue implicazioni e le migliori pratiche per sfruttarlo efficacemente.<\/p>\n

What is Docker Caching?<\/h2>\n

Per capire --cache-overhead<\/code>, Per prima cosa, dobbiamo comprendere il concetto di Docker caching. Quando si costruisce un'immagine Docker... 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>, \u00e8 costituito da pi\u00f9 strati, ognuno dei quali rappresenta un passo nel 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 intelligently caches these layers, meaning that if the same command is executed again during a build, Docker will reuse the cached layer rather than re-executing the command. This can significantly speed up the build process, especially for large images or complex applications.<\/p>\n

The caching mechanism is based on the idea that layers are immutable; if any part of a layer changes, all subsequent layers need to be rebuilt. Consequently, developers often structure their Dockerfiles to maximize the cache\u2019s effectiveness, keeping frequently changing commands towards the end of the file and stable commands at the beginning.<\/p>\n

The Role of \u2013cache-overhead<\/h2>\n

The --cache-overhead<\/code> flag is an advanced feature that allows developers to specify additional computational overhead that should be taken into account when determining whether a cached layer can be reused. By default, Docker manages caching based solely on the output of commands; however, there are scenarios where this can lead to sub-optimal caching decisions\u2014especially in complex builds where multiple layers interact.<\/p>\n

Perch\u00e9 usare \u2013cache-overhead?<\/h3>\n

Usando il --cache-overhead<\/code> La bandiera pu\u00f2 portare a diversi vantaggi:<\/p>\n

    \n
  1. \n

    Controllo granulare<\/strong>: Developers can explicitly define how sensitive their builds are to changes in layers. For instance, if a certain operation is expected to vary frequently, applying a higher overhead can reduce the risk of unnecessary cache invalidation.<\/p>\n<\/li>\n

  2. \n

    Miglioramento delle prestazioni<\/strong>: By reducing the frequency of cache invalidation, builds can become noticeably faster. This is particularly beneficial in Continuous Integration\/Continuous Deployment (CI\/CD) pipelines, where build times are critical.<\/p>\n<\/li>\n

  3. \n

    Ottimizzazione delle Risorse<\/strong>: Managing cache overhead allows teams to make more efficient use of their computational resources, minimizing wasted effort on rebuilds and reducing overall system load.<\/p>\n<\/li>\n<\/ol>\n

    How to Use \u2013cache-overhead<\/h2>\n

    Sintassi e opzioni<\/h3>\n

    The --cache-overhead<\/code> flag can be used during the build process via the command line. The syntax is straightforward:<\/p>\n

    docker build --cache-overhead=VALORE .<\/code><\/pre>\n
    Where VALORE<\/code> represents the computational overhead that should be considered. This value can be a percentage or a fixed amount, depending on the context of the build and the specific requirements of the application.<\/p>\n
    Esempio di utilizzo<\/h3>\n
    Consideriamo un esempio pratico in cui uno sviluppatore sta costruendo un'applicazione a pi\u00f9 fasi. In questo scenario, lo sviluppatore potrebbe voler impostare un overhead di cache specifico per una delle fasi di build:<\/p>\n
    # Stage 1: Build the application\nFROM node<\/a><\/span>Node, or Node.js, is a JavaScript runtime built on Chrome's V8 engine, enabling server-side scripting. It allows developers to build scalable network applications using asynchronous, event-driven architecture. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>:14 Come costruttore\nWORKDIR<\/a><\/span>L'istruzione `WORKDIR` nel Dockerfile imposta la directory di lavoro per le istruzioni successive. Semplifica la gestione dei percorsi, poich\u00e9 tutti i percorsi relativi verranno risolti a partire da questa directory, migliorando la chiarezza della build. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> \/app\nCOPIA<\/a><\/span>COPY \u00e8 un comando nella programmazione informatica e nella gestione dei dati che facilita la duplicazione di file o dati da una posizione a un'altra, garantendo l'integrit\u00e0 e l'accessibilit\u00e0 dei dati. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> package.json .\/\nRUN<\/a><\/span>\"RUN\" si riferisce a un comando in diversi linguaggi di programmazione e sistemi operativi per eseguire un programma o script specificato. Avvia processi, fornendo un ambiente controllato per l'esecuzione dei compiti. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> npm install\n\n# Stage 2: Create the final image\nFROM nginx:alpine\nCOPIA<\/a><\/span>COPY \u00e8 un comando nella programmazione informatica e nella gestione dei dati che facilita la duplicazione di file o dati da una posizione a un'altra, garantendo l'integrit\u00e0 e l'accessibilit\u00e0 dei dati. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> --from=builder \/app\/build \/usr\/share\/nginx\/html<\/code><\/pre>\n
    In this case, if the npm install<\/code> command is expected to change frequently (e.g., due to changing package versions or added dependencies), you can correre<\/a><\/span>\"RUN\" si riferisce a un comando in diversi linguaggi di programmazione e sistemi operativi per eseguire un programma o script specificato. Avvia processi, fornendo un ambiente controllato per l'esecuzione dei compiti. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> the build with a higher cache overhead:<\/p>\n
    docker build --cache-overhead=20% -t my-application .<\/code><\/pre>\n
    This command instructs Docker to consider a 20% overhead on the npm install<\/code> cache layer. <\/p>\n
    When to Be Cautious with \u2013cache-overhead<\/h2>\n
    Mentre il --cache-overhead<\/code> Sebbene la bandiera offra numerosi vantaggi, \u00e8 essenziale utilizzarla con giudizio. Ecco alcuni scenari in cui \u00e8 necessaria cautela:<\/p>\n
      \n
    1. \n
      Complessit\u00e0 Aumentata<\/strong>: L'introduzione di overhead di cache pu\u00f2 aggiungere<\/a><\/span>L'istruzione ADD in Docker \u00e8 un comando utilizzato nei Dockerfile per copiare file e directory da una macchina host in un'immagine Docker durante il processo di build. Non solo semplifica il trasferimento di file locali, ma fornisce anche funzionalit\u00e0 aggiuntive, come l'estrazione automatica di file compressi e il download di file remoti tramite HTTP o HTTPS. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> complexity to the build process. It may not always be clear how the overhead is calculated and applied, potentially leading to confusion.<\/p>\n<\/li>\n
    2. \n
      Costruzioni Sub-ottimali<\/strong>: Setting an overhead that is too high can lead to stale layers being reused, which may inadvertently introduce bugs or inconsistencies in the application.<\/p>\n<\/li>\n
    3. \n
      Sfide di test e debug<\/strong>Quando si eseguono debug di problemi relativi alle build, avere un overhead pu\u00f2 complicare il processo di indagine, rendendo pi\u00f9 difficile individuare dove sorgono i problemi.<\/p>\n<\/li>\n<\/ol>\n
      Migliori pratiche per l'uso di \u2013cache-overhead<\/h2>\n
      To make the best use of the --cache-overhead<\/code> bandiera, considera le seguenti best practice:<\/p>\n
      1. Assess Build Stability<\/h3>\n
      Prima di applicare un overhead, valuta con quale frequenza \u00e8 probabile che il comando o il livello cambi. Se i cambiamenti sono infrequenti, potrebbe essere sufficiente un overhead inferiore.<\/p>\n
      2. Monitoraggio delle Prestazioni di Build<\/h3>\n
      Use Docker\u2019s build performance monitoring tools to analyze build times with and without the --cache-overhead<\/code> flag. Questi dati possono aiutarti a prendere decisioni informate su come configurare la cache per il tuo caso d'uso specifico.<\/p>\n
      3. Enfatizzare la Struttura a Strati<\/h3>\n
      Structure your 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> to maximize caching efficiency. Place rarely changed commands at the top of your 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> and frequently changed commands at the bottom. This structure will minimize the impact of cache overhead on your overall build time.<\/p>\n
      4. Motivazione dei costi generali di documentazione<\/h3>\n
      As with any advanced feature, it\u2019s crucial to document why certain overhead values were chosen. This documentation will help your team understand the rationale behind build decisions and ease the onboarding process for new developers.<\/p>\n
      5. Test Thoroughly<\/h3>\n
      Prima di implementare qualsiasi modifica alle build di produzione, eseguire test approfonditi per garantire che l'applicazione si comporti come previsto e che l'overhead della cache stia ottenendo i miglioramenti delle prestazioni desiderati.<\/p>\n
      The Future of Docker Caching<\/h2>\n
      As containerization continues to evolve, the approach to caching will likely become more sophisticated. The introduction of --cache-overhead<\/code> Questo \u00e8 solo un esempio di come Docker stia migliorando i suoi meccanismi di caching per soddisfare le diverse esigenze degli sviluppatori. Gli aggiornamenti futuri potrebbero includere opzioni di controllo ancora pi\u00f9 granulari e strategie pi\u00f9 intelligenti per l'invalidazione dei layer.<\/p>\n
      Container Orchestration and Caching<\/h3>\n
      Con l'ascesa di container<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> orchestrazione<\/a><\/span>Orchestration refers to the automated management and coordination of complex systems and services. It optimizes processes by integrating various components, ensuring efficient operation and resource utilization. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> piattaforme come Kubernetes<\/a><\/span>Kubernetes is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications, enhancing resource efficiency and resilience. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>, understanding and optimizing Docker 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 will become even more critical. As teams deploy microservices and scale applications, the efficiency of 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> building directly impacts deployment times and resource utilization.<\/p>\n
      Comunit\u00e0 e Contributo<\/h3>\n
      The Docker community is an invaluable resource for learning about best practices and advanced features like --cache-overhead<\/code>. Engaging with the community through forums, GitHub issues, and conferences can provide insights that help you optimize your containerization strategies.<\/p>\n
      Conclusione<\/h2>\n
      The --cache-overhead<\/code> flag di ingresso 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 powerful tool that enables developers to optimize build times and resource utilization. By understanding its functionality and implications, teams can craft more efficient and maintainable Docker images. However, caution and best practices must be observed to ensure that the benefits outweigh any potential downsides. As the landscape of containerization evolves, staying informed about features like --cache-overhead<\/code> sar\u00e0 cruciale per gli sviluppatori che desiderano sfruttare appieno il potenziale di Docker.<\/p>","protected":false},"excerpt":{"rendered":"
      The `\u2013cache-overhead` 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> builds allows users to specify the proportion of cache usage relative to the build context. This parameter optimizes caching efficiency, enhancing build performance while managing resource consumption.<\/p>","protected":false},"author":1,"featured_media":2093,"parent":0,"template":"","glossary-cat":[],"class_list":["post-1390","glossary","type-glossary","status-publish","has-post-thumbnail","hentry"],"yoast_head":"\nDockerfile -cache-overhead - 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\/sovraccarico-della-cache-del-dockerfile\/\" \/>\n<meta property=\"og:locale\" content=\"it_IT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Dockerfile -cache-overhead - Dockerpros\" \/>\n<meta property=\"og:description\" content=\"The `--cache-overhead` option in Dockerfile builds allows users to specify the proportion of cache usage relative to the build context. This parameter optimizes caching efficiency, enhancing build performance while managing resource consumption.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dockerpros.com\/it\/wiki\/sovraccarico-della-cache-del-dockerfile\/\" \/>\n<meta property=\"og:site_name\" content=\"Dockerpros\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-cache-overhead_1390.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=\"5 minuti\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/\",\"url\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/\",\"name\":\"Dockerfile -cache-overhead - Dockerpros\",\"isPartOf\":{\"@id\":\"https:\/\/dockerpros.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-cache-overhead_1390.jpg\",\"datePublished\":\"2024-07-23T12:39:25+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#breadcrumb\"},\"inLanguage\":\"it-IT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#primaryimage\",\"url\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-cache-overhead_1390.jpg\",\"contentUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-cache-overhead_1390.jpg\",\"width\":800,\"height\":600,\"caption\":\"dockerfile-cache-overhead-2\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#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 –cache-overhead\"}]},{\"@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 -sovraccarico-della-cache - Dockerpros","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\/sovraccarico-della-cache-del-dockerfile\/","og_locale":"it_IT","og_type":"article","og_title":"Dockerfile -cache-overhead - Dockerpros","og_description":"The `--cache-overhead` option in Dockerfile builds allows users to specify the proportion of cache usage relative to the build context. This parameter optimizes caching efficiency, enhancing build performance while managing resource consumption.","og_url":"https:\/\/dockerpros.com\/it\/wiki\/sovraccarico-della-cache-del-dockerfile\/","og_site_name":"Dockerpros","og_image":[{"width":800,"height":600,"url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-cache-overhead_1390.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Tempo di lettura stimato":"5 minuti"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/","url":"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/","name":"Dockerfile -sovraccarico-della-cache - Dockerpros","isPartOf":{"@id":"https:\/\/dockerpros.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#primaryimage"},"image":{"@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#primaryimage"},"thumbnailUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-cache-overhead_1390.jpg","datePublished":"2024-07-23T12:39:25+00:00","breadcrumb":{"@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#breadcrumb"},"inLanguage":"it-IT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/"]}]},{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#primaryimage","url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-cache-overhead_1390.jpg","contentUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-cache-overhead_1390.jpg","width":800,"height":600,"caption":"dockerfile-cache-overhead-2"},{"@type":"BreadcrumbList","@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-cache-overhead\/#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 –cache-overhead"}]},{"@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\/1390","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\/1390\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/media\/2093"}],"wp:attachment":[{"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/media?parent=1390"}],"wp:term":[{"taxonomy":"glossary-cat","embeddable":true,"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/glossary-cat?post=1390"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}