{"id":1335,"date":"2024-07-23T12:21:45","date_gmt":"2024-07-23T12:21:45","guid":{"rendered":"https:\/\/dockerpros.com\/?post_type=glossary&p=1335"},"modified":"2024-07-23T12:23:52","modified_gmt":"2024-07-23T12:23:52","slug":"dockerfile-force-rm","status":"publish","type":"glossary","link":"https:\/\/dockerpros.com\/it\/wiki\/dockerfile-force-rm\/","title":{"rendered":"Dockerfile \u2013force-rm"},"content":{"rendered":"

Comprensione del flag --force-rm in Dockerfile: Un'Esplorazione Approfondita<\/h1>\n

Al suo centro, --force-rm<\/code> is a build option in Docker that dictates whether intermediate containers created during the build process should be removed automatically, even if the build fails. This command-line option can be vital for maintaining a clean environment, preventing the accumulation of unnecessary intermediate containers, and optimizing the overall Docker workflow. In this article, we will delve into the intricacies of --force-rm<\/code>, esaminandone l'utilizzo, i vantaggi e le best practice, nonch\u00e9 le sue implicazioni per 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> costruzioni.<\/p>\n

Docker Build Process: Una breve panoramica<\/h2>\n

Before diving into --force-rm<\/code>, \u00e8 essenziale comprendere il Docker image build<\/a><\/span>Docker image build is a process that creates a Docker image from a set of instructions defined in a Dockerfile. It encapsulates an application and its dependencies, ensuring consistent deployment across environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> process. When you 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> docker build<\/code>, Docker reads the instructions from 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><\/code> and creates 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> layer by layer. Each instruction 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><\/code> genera un intermedio 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>. These intermediate containers serve as the base for the next instruction or layer. However, if a build fails, these intermediate containers may remain on the system, consuming disk space and cluttering the Docker environment.<\/p>\n

The Role of Intermediate Containers<\/h3>\n

Intermediate containers are temporary by nature. They exist solely to facilitate the 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 process. By default, Docker retains these containers even when a build fails, allowing users to inspect them for debugging purposes. However, this can lead to a situation known as "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> bloat," where numerous leftover containers consume valuable system resources. This is where the --force-rm<\/code> flag becomes instrumental.<\/p>\n

The --force-rm<\/code> Flag: Definition and Use<\/h2>\n

The --force-rm<\/code> la flag viene utilizzata con il docker build<\/code> comando per rimuovere automaticamente tutti i contenitori intermedi, indipendentemente dal fatto che la build vada a buon fine o fallisca. La sua sintassi \u00e8 la seguente:<\/p>\n

docker build --force-rm -t my_image:latest .<\/code><\/pre>\n
In questo esempio, il -<\/code> flag tags the 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> with a given name and version, while the --force-rm<\/code> Il flag garantisce che tutti i contenitori intermedi creati durante la build verranno rimossi una volta terminato il processo di build.<\/p>\n
Quando usare --force-rm<\/code><\/h3>\n
Usando --force-rm<\/code> \u00e8 particolarmente vantaggioso negli scenari in cui:<\/p>\n
    \n
  1. \n
    Frequent Builds<\/strong>Gli sviluppatori spesso costruiscono immagini pi\u00f9 volte durante il ciclo di sviluppo. Utilizzando --force-rm<\/code> can help keep systems tidy by removing unnecessary intermediate containers after each build.<\/p>\n<\/li>\n
  2. \n
    Limited Disk Space<\/strong>: Se si opera in un ambiente con capacit\u00e0 di disco limitata, come pipeline CI\/CD o macchine virtuali di piccole dimensioni, questa opzione aiuta a evitare problemi di spazio su disco.<\/p>\n<\/li>\n
  3. \n
    Processi automatizzati<\/strong>: In automated build environments, such as Docker CI\/CD setups, it\u2019s crucial to maintain a clean workspace. Using --force-rm<\/code> can help ensure that no remnants from previous builds linger.<\/p>\n<\/li>\n
  4. \n
    Debugging<\/strong>: Although --force-rm<\/code> removes intermediate containers, it can also be a good practice to use it alongside debugging tools and logs to ensure that error handling is managed separately, reducing the clutter you have to sift through.<\/p>\n<\/li>\n<\/ol>\n
    Advantages of Using --force-rm<\/code><\/h2>\n
    Mentre --force-rm<\/code> is a simple flag, its implications for the Docker build process are substantial. Here are some of the notable advantages:<\/p>\n
    1. Build Puliti<\/h3>\n
    Con --force-rm<\/code>, gli sviluppatori possono essere pi\u00f9 sicuri che il loro ambiente di build sia pulito e privo di residui di build precedenti. Questo aiuta a prevenire comportamenti inaspettati che possono derivare da contenitori residui.<\/p>\n
    2. Utilizzo efficiente del disco<\/h3>\n
    Lo spazio su disco \u00e8 spesso limitato, specialmente negli ambienti di sviluppo o produzione. Using --force-rm<\/code> can save valuable disk space by ensuring that intermediate containers don\u2019t accumulate unnecessarily.<\/p>\n
    3. Improved Build Performance<\/h3>\n
    While not directly related to the build’s speed, reducing the number of intermediate containers can improve the overall performance of Docker command execution in the long 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>. Fewer containers mean less overhead in managing them.<\/p>\n
    4. Simplified Troubleshooting<\/h3>\n
    Nei casi in cui le compilazioni falliscono, gli sviluppatori possono concentrarsi sullo stato non riuscito senza dover esaminare i container intermedi. Questa semplificazione pu\u00f2 portare a sessioni di debug pi\u00f9 rapide e a una risoluzione pi\u00f9 veloce dei problemi.<\/p>\n
    Disadvantages of Using --force-rm<\/code><\/h2>\n
    Sebbene i vantaggi siano significativi, ci sono alcuni compromessi e potenziali svantaggi da considerare:<\/p>\n
    1. Perdita di informazioni di debug<\/h3>\n
    Una delle ragioni principali per mantenere i contenitori intermedi \u00e8 facilitare la risoluzione dei problemi. Se una build fallisce, gli sviluppatori possono indagare sull'ultimo passo riuscito ispezionando i contenitori intermedi. Con --force-rm<\/code>, questa opportunit\u00e0 viene persa, il che pu\u00f2 complicare gli sforzi di debug.<\/p>\n
    2. Slower Build Iterations<\/h3>\n
    In some cases, keeping intermediate containers can actually speed up subsequent builds through Docker\u2019s caching mechanism. If --force-rm<\/code> viene utilizzato troppo liberamente, questo vantaggio della cache pu\u00f2 diminuire, portando a tempi di build pi\u00f9 lunghi in determinati scenari.<\/p>\n
    3. Utilizzo accidentale in produzione<\/h3>\n
    Negli ambienti di produzione, gli sviluppatori potrebbero accidentalmente utilizzare --force-rm<\/code> senza comprendere appieno le sue implicazioni. Ci\u00f2 pu\u00f2 portare a conseguenze non intenzionali, specialmente se \u00e8 necessario eseguire il debug dopo la distribuzione.<\/p>\n
    Best Practices for Using --force-rm<\/code><\/h2>\n
    Per sfruttare al meglio il --force-rm<\/code> flag while minimizing its drawbacks, consider these best practices:<\/p>\n
    1. Uso in Ambienti di Sviluppo<\/h3>\n
    Utilizzo --force-rm<\/code> primarily in development and testing environments rather than production. This allows for cleaner builds and optimization without sacrificing the ability to debug builds when needed.<\/p>\n
    2. Combinalo con una registrazione adeguata<\/h3>\n
    When using --force-rm<\/code>, ensure that all relevant logs are captured elsewhere. This way, even if intermediate containers are removed, you can still reference logs to understand what went wrong during the build process.<\/p>\n
    3. Sfruttare Docker BuildKit<\/h3>\n
    Consider using Docker BuildKit, which is an advanced builder for Docker that offers improved performance and caching strategies compared to traditional builds. It may reduce the need for using --force-rm<\/code> as BuildKit manages intermediate layers more efficiently.<\/p>\n
    4. Keep an Eye on Disk Usage<\/h3>\n
    Monitor disk usage regularly, especially in CI\/CD environments. While --force-rm<\/code> helps, it\u2019s still essential to have a broader strategy for managing Docker images and containers to prevent bloating.<\/p>\n
    5. Document Build Processes<\/h3>\n
    Ensure your team is informed about the implications of using --force-rm<\/code>. Una documentazione e formazione adeguate possono aiutare gli sviluppatori a evitare potenziali trappole e a sfruttare appieno le funzionalit\u00e0 di Docker.<\/p>\n
    Conclusione<\/h2>\n
    The --force-rm<\/code> flag is a powerful tool in Docker\u2019s arsenal, providing developers with the capability to manage intermediate containers effectively during the 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> build process. By understanding its functionality, benefits, and trade-offs, developers can make informed decisions about when and how to use this option. As with many Docker features, the key to effectively utilizing --force-rm<\/code> lies in understanding the broader context of the Docker workflow and aligning tool usage with specific development needs.<\/p>\n
    Implementando le migliori pratiche e considerando attentamente quando impiegare --force-rm<\/code>, gli sviluppatori possono mantenere un ambiente Docker pulito ed efficiente che supporta cicli di sviluppo e distribuzione rapidi. In definitiva, l'obiettivo \u00e8 trovare un equilibrio tra pulizia della build, prestazioni e capacit\u00e0 di risolvere efficacemente i problemi, assicurando che Docker serva come uno strumento robusto nella cassetta degli attrezzi di sviluppo.<\/p>","protected":false},"excerpt":{"rendered":"
    The `\u2013force-rm` 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> La costruzione garantisce che i contenitori intermedi vengano rimossi anche se la build fallisce. Ci\u00f2 contribuisce a mantenere un ambiente pi\u00f9 pulito e a conservare spazio su disco durante la 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> creation process.<\/p>","protected":false},"author":1,"featured_media":1983,"parent":0,"template":"","glossary-cat":[],"class_list":["post-1335","glossary","type-glossary","status-publish","has-post-thumbnail","hentry"],"yoast_head":"\nDockerfile -force-rm - 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-force-rm\/\" \/>\n<meta property=\"og:locale\" content=\"it_IT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Dockerfile -force-rm - Dockerpros\" \/>\n<meta property=\"og:description\" content=\"The `--force-rm` option in Dockerfile builds ensures that intermediate containers are removed even if the build fails. This helps maintain a cleaner environment and conserves disk space during the image creation process.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dockerpros.com\/it\/wiki\/dockerfile-force-rm\/\" \/>\n<meta property=\"og:site_name\" content=\"Dockerpros\" \/>\n<meta property=\"article:modified_time\" content=\"2024-07-23T12:23:52+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-force-rm_1335.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\/fr\/wiki\/dockerfile-force-rm\/\",\"url\":\"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/\",\"name\":\"Dockerfile -force-rm - Dockerpros\",\"isPartOf\":{\"@id\":\"https:\/\/dockerpros.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-force-rm_1335.jpg\",\"datePublished\":\"2024-07-23T12:21:45+00:00\",\"dateModified\":\"2024-07-23T12:23:52+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#breadcrumb\"},\"inLanguage\":\"it-IT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#primaryimage\",\"url\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-force-rm_1335.jpg\",\"contentUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-force-rm_1335.jpg\",\"width\":800,\"height\":600,\"caption\":\"dockerfile-force-rm-2\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#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 –force-rm\"}]},{\"@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 -force-rm - 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\/dockerfile-force-rm\/","og_locale":"it_IT","og_type":"article","og_title":"Dockerfile -force-rm - Dockerpros","og_description":"The `--force-rm` option in Dockerfile builds ensures that intermediate containers are removed even if the build fails. This helps maintain a cleaner environment and conserves disk space during the image creation process.","og_url":"https:\/\/dockerpros.com\/it\/wiki\/dockerfile-force-rm\/","og_site_name":"Dockerpros","article_modified_time":"2024-07-23T12:23:52+00:00","og_image":[{"width":800,"height":600,"url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-force-rm_1335.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\/fr\/wiki\/dockerfile-force-rm\/","url":"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/","name":"Dockerfile -force-rm - Dockerpros","isPartOf":{"@id":"https:\/\/dockerpros.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#primaryimage"},"image":{"@id":"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#primaryimage"},"thumbnailUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-force-rm_1335.jpg","datePublished":"2024-07-23T12:21:45+00:00","dateModified":"2024-07-23T12:23:52+00:00","breadcrumb":{"@id":"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#breadcrumb"},"inLanguage":"it-IT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/"]}]},{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#primaryimage","url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-force-rm_1335.jpg","contentUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-force-rm_1335.jpg","width":800,"height":600,"caption":"dockerfile-force-rm-2"},{"@type":"BreadcrumbList","@id":"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-force-rm\/#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 –force-rm"}]},{"@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\/1335","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\/1335\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/media\/1983"}],"wp:attachment":[{"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/media?parent=1335"}],"wp:term":[{"taxonomy":"glossary-cat","embeddable":true,"href":"https:\/\/dockerpros.com\/it\/wp-json\/wp\/v2\/glossary-cat?post=1335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}