{"id":1355,"date":"2024-07-23T12:37:58","date_gmt":"2024-07-23T12:37:58","guid":{"rendered":"https:\/\/dockerpros.com\/?post_type=glossary&p=1355"},"modified":"2024-07-23T12:37:58","modified_gmt":"2024-07-23T12:37:58","slug":"dockerfile-export-cache","status":"publish","type":"glossary","link":"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-export-cache\/","title":{"rendered":"Dockerfile \u2013export-cache"},"content":{"rendered":"

Understanding Dockerfile \u2013export-cache: Accelerating Your Build Process<\/h2>\n

In the world of containerization, efficiency is paramount. The Dockerfile<\/a><\/span>A Dockerfile is a script containing a series of instructions to automate the creation of Docker images. It specifies the base image, application dependencies, and configuration, facilitating consistent deployment across environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> --exporter-cache<\/code> option is a powerful feature that allows developers to export build cache layers from a contexte de construction<\/a><\/span>Le contexte de build Docker d\u00e9signe les fichiers et r\u00e9pertoires disponibles lors de la construction de l'image. Il est essentiel pour acc\u00e9der au code et aux d\u00e9pendances de l'application, ce qui influence l'efficacit\u00e9 et la s\u00e9curit\u00e9. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> to a specified location. This feature not only optimizes the build process by reducing build times but also enhances the reusability of cached layers across different Docker builds. In this article, we will delve into the intricacies of --exporter-cache<\/code>, en explorant sa syntaxe, ses cas d'utilisation, ses avantages et les bonnes pratiques pour l'impl\u00e9menter dans vos workflows Docker.<\/p>\n

Qu'est-ce que le cache de construction Docker ?<\/h2>\n

Before delving into --exporter-cache<\/code>, il est essentiel de comprendre le concept de Cache de construction Docker<\/a><\/span>Docker Build Cache optimizes the image building process by storing intermediate layers. This reduces build time and resource consumption, allowing developers to efficiently manage dependencies and streamline workflows. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>. Lorsque vous construisez un image<\/a><\/span>Une image est une repr\u00e9sentation visuelle d'un objet ou d'une sc\u00e8ne, g\u00e9n\u00e9ralement compos\u00e9e de pixels dans les formats num\u00e9riques. Elle peut transmettre des informations, susciter des \u00e9motions et faciliter la communication \u00e0 travers diff\u00e9rents m\u00e9dias. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> \u00e0 partir d'un Dockerfile<\/a><\/span>A Dockerfile is a script containing a series of instructions to automate the creation of Docker images. It specifies the base image, application dependencies, and configuration, facilitating consistent deployment across environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>, Docker caches the results of each step of the build process. If you run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> the same build again, Docker can reuse these cached layers instead of executing them again, which significantly speeds up the build time.<\/p>\n

For instance, if your Dockerfile<\/a><\/span>A Dockerfile is a script containing a series of instructions to automate the creation of Docker images. It specifies the base image, application dependencies, and configuration, facilitating consistent deployment across environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> contains multiple steps, and only the last step has changed, Docker will skip the previous steps that haven’t changed, utilizing the cached layers. This is particularly beneficial in CI\/CD pipelines, where time is of the essence.<\/p>\n

The Role of \u2013export-cache<\/h2>\n

Avec le --exporter-cache<\/code> option, les d\u00e9veloppeurs peuvent exporter les couches de cache vers un r\u00e9pertoire local, ce qui permet un partage et une r\u00e9utilisation plus faciles de ces couches mises en cache dans diff\u00e9rents environnements, voire sur diff\u00e9rentes machines. Cela est particuli\u00e8rement utile lors du travail en \u00e9quipe ou sur des syst\u00e8mes CI\/CD, o\u00f9 les environnements de construction peuvent varier.<\/p>\n

Syntax and Usage<\/h3>\n

Pour utiliser le --exporter-cache<\/code> option, vous l'invoqueriez typiquement dans le cadre de la docker build<\/code> commande. La syntaxe est la suivante :<\/p>\n

docker build --export-cache=path\/to\/cache .<\/code><\/pre>\n
Here, chemin\/vers\/cache<\/code> is the directory where the exported cache layers will be stored. This command builds the Docker image<\/a><\/span>Une image est une repr\u00e9sentation visuelle d'un objet ou d'une sc\u00e8ne, g\u00e9n\u00e9ralement compos\u00e9e de pixels dans les formats num\u00e9riques. Elle peut transmettre des informations, susciter des \u00e9motions et faciliter la communication \u00e0 travers diff\u00e9rents m\u00e9dias. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> defined by the current directory (denoted by .<\/code>) while exporting the cache layers to the specified location.<\/p>\n
Example of Using \u2013export-cache<\/h3>\n
Prenons un exemple pratique pour illustrer comment --exporter-cache<\/code> can be utilized. Suppose you have a Dockerfile<\/a><\/span>A Dockerfile is a script containing a series of instructions to automate the creation of Docker images. It specifies the base image, application dependencies, and configuration, facilitating consistent deployment across environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> that installs multiple dependencies and builds a web application. You can decide to export the cache after the initial stages of building, which usually take the most time.<\/p>\n
# Dockerfile<\/a><\/span>A Dockerfile is a script containing a series of instructions to automate the creation of Docker images. It specifies the base image, application dependencies, and configuration, facilitating consistent deployment across environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> example\nFROM n\u0153ud<\/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\n\nWORKDIR<\/a><\/span>L'instruction `WORKDIR` dans le Dockerfile d\u00e9finit le r\u00e9pertoire de travail pour les instructions suivantes. Elle simplifie la gestion des chemins, car tous les chemins relatifs seront r\u00e9solus \u00e0 partir de ce r\u00e9pertoire, am\u00e9liorant ainsi la clart\u00e9 de la construction. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> \/app\n\n# Installer les d\u00e9pendances\nCOPIE<\/a><\/span>COPY is a command in computer programming and data management that facilitates the duplication of files or data from one location to another, ensuring data integrity and accessibility. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> package.json package-lock.json .\/\nRUN<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> npm install\n\n# Copier<\/a><\/span>COPY is a command in computer programming and data management that facilitates the duplication of files or data from one location to another, ensuring data integrity and accessibility. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> application code\nCOPIE<\/a><\/span>COPY is a command in computer programming and data management that facilitates the duplication of files or data from one location to another, ensuring data integrity and accessibility. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> . .\n\n# Build the application\nRUN<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> npm run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> construire<\/code><\/pre>\n
Tu peux run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> the following command to build the image<\/a><\/span>Une image est une repr\u00e9sentation visuelle d'un objet ou d'une sc\u00e8ne, g\u00e9n\u00e9ralement compos\u00e9e de pixels dans les formats num\u00e9riques. Elle peut transmettre des informations, susciter des \u00e9motions et faciliter la communication \u00e0 travers diff\u00e9rents m\u00e9dias. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> while exporting the cache:<\/p>\n
docker build --export-cache=.\/cache .<\/code><\/pre>\n
This command will build your Docker image<\/a><\/span>Une image est une repr\u00e9sentation visuelle d'un objet ou d'une sc\u00e8ne, g\u00e9n\u00e9ralement compos\u00e9e de pixels dans les formats num\u00e9riques. Elle peut transmettre des informations, susciter des \u00e9motions et faciliter la communication \u00e0 travers diff\u00e9rents m\u00e9dias. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> and store the cache layers in the .\/cache<\/code> directory. If you subsequently run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> the build again, Docker will be able to leverage these cached layers, significantly speeding up the process.<\/p>\n
Advantages of Using \u2013export-cache<\/h2>\n
1. Am\u00e9lioration des performances de construction<\/h3>\n
L'avantage principal de l'utilisation --exporter-cache<\/code> is the enhanced performance during image<\/a><\/span>Une image est une repr\u00e9sentation visuelle d'un objet ou d'une sc\u00e8ne, g\u00e9n\u00e9ralement compos\u00e9e de pixels dans les formats num\u00e9riques. Elle peut transmettre des informations, susciter des \u00e9motions et faciliter la communication \u00e0 travers diff\u00e9rents m\u00e9dias. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> builds. By caching layers and exporting them, subsequent builds can bypass lengthy installation processes, thereby reducing build times drastically.<\/p>\n
2. Partage de cache entre membres de l'\u00e9quipe<\/h3>\n
Dans les environnements collaboratifs, les membres de l'\u00e9quipe peuvent avoir des configurations locales diff\u00e9rentes, entra\u00eenant des incoh\u00e9rences dans les temps de construction. En exportant un cache partag\u00e9, les \u00e9quipes peuvent s'assurer que tout le monde utilise les m\u00eames couches pr\u00e9-construites, nivelant ainsi le terrain de jeu et r\u00e9duisant le temps pass\u00e9 \u00e0 attendre les constructions.<\/p>\n
3. Int\u00e9gration CI\/CD simplifi\u00e9e<\/h3>\n
In continuous integration\/continuous deployment (CI\/CD) setups, build times can become a bottleneck. By using --exporter-cache<\/code>, les organisations peuvent cr\u00e9er une couche de cache qui peut \u00eatre r\u00e9utilis\u00e9e dans diff\u00e9rents pipelines de construction. Cela peut \u00eatre particuli\u00e8rement efficace dans les constructions multi-\u00e9tapes, o\u00f9 certaines \u00e9tapes peuvent \u00eatre mises en cache ind\u00e9pendamment.<\/p>\n
4. Version Control for Caches<\/h3>\n
Exporting caches to a specific directory allows developers to manage different cache versions easily. This enables them to roll back to previous cache versions when necessary, ensuring that builds remain stable even if the underlying code changes.<\/p>\n
Bonnes pratiques pour l'utilisation de \u2013export-cache<\/h2>\n
1. Gardez votre cache organis\u00e9<\/h3>\n
Lors de l'exportation des couches de cache, il est crucial de maintenir une structure de r\u00e9pertoire bien organis\u00e9e. Envisagez d'utiliser des dossiers horodat\u00e9s ou des num\u00e9ros de version pour garder les caches s\u00e9par\u00e9s. Cette pratique vous aidera \u00e0 g\u00e9rer vos caches efficacement et \u00e0 \u00e9viter toute confusion \u00e0 l'avenir.<\/p>\n
2. Use .dockerignore<\/h3>\n
Pour \u00e9viter que des fichiers inutiles ne soient inclus dans le cache, utilisez toujours un m\u00e9canisme d'exclusion. .dockerignore<\/code> file. This file will help you filter out files and directories that do not need to be part of the contexte de construction<\/a><\/span>Le contexte de build Docker d\u00e9signe les fichiers et r\u00e9pertoires disponibles lors de la construction de l'image. Il est essentiel pour acc\u00e9der au code et aux d\u00e9pendances de l'application, ce qui influence l'efficacit\u00e9 et la s\u00e9curit\u00e9. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>, thus optimizing both your cache and overall image<\/a><\/span>Une image est une repr\u00e9sentation visuelle d'un objet ou d'une sc\u00e8ne, g\u00e9n\u00e9ralement compos\u00e9e de pixels dans les formats num\u00e9riques. Elle peut transmettre des informations, susciter des \u00e9motions et faciliter la communication \u00e0 travers diff\u00e9rents m\u00e9dias. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> taille.<\/p>\n
3. Combiner avec \u2013import-cache<\/h3>\n
Docker also provides the option to import previously exported caches using the --import-cache<\/code> flag. Combining both --exporter-cache<\/code> and --import-cache<\/code> vous permet de maximiser les avantages de la mise en cache. Vous pouvez exporter un cache d'une construction et l'importer dans une autre, ce qui facilite la gestion des d\u00e9pendances partag\u00e9es entre plusieurs projets ou microservices.<\/p>\n
docker build --import-cache=.\/cache --export-cache=.\/new_cache .<\/code><\/pre>\n
4. Monitor Cache Size<\/h3>\n
Comme avec tout m\u00e9canisme de cache, la taille de votre cache peut augmenter avec le temps, consommant un espace disque pr\u00e9cieux. Surveillez r\u00e9guli\u00e8rement la taille de votre r\u00e9pertoire de cache et nettoyez-le si n\u00e9cessaire. Vous pouvez utiliser des outils tels que du<\/code> pour \u00e9valuer l'utilisation du disque de votre r\u00e9pertoire de cache.<\/p>\n
5. Profile Your Builds<\/h3>\n
Pour d\u00e9terminer quelles couches prennent le plus de temps, envisagez de profiler vos builds Docker. Vous pouvez utiliser le --progress=plain<\/code> option avec les constructions Docker pour obtenir une sortie de construction d\u00e9taill\u00e9e, ce qui peut vous aider \u00e0 identifier les goulots d'\u00e9tranglement dans votre processus de construction. Rem\u00e9dier \u00e0 ces goulots d'\u00e9tranglement peut r\u00e9duire le besoin d'une mise en cache \u00e9tendue.<\/p>\n
docker build --progress=plain --export-cache=.\/cache .<\/code><\/pre>\n
Troubleshooting Common Issues<\/h2>\n
Les d\u00e9fauts de cache<\/h3>\n
One of the most common issues when working with Docker caches is encountering cache misses. This occurs when Docker cannot use a cached layer because the context has changed. To mitigate this, ensure that the order of commands in your Dockerfile<\/a><\/span>A Dockerfile is a script containing a series of instructions to automate the creation of Docker images. It specifies the base image, application dependencies, and configuration, facilitating consistent deployment across environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> is optimized. Layers that are less likely to change (e.g., installations) should be placed before those that change frequently (e.g., code copies).<\/p>\n
Contraintes d'espace disque<\/h3>\n
If you find that your cache is consuming too much disk space, consider setting up a routine to clean unused caches. Docker provides commands to prune dangling images and unused volumes, which can help manage disk usage.<\/p>\n
docker system prune -af<\/code><\/pre>\n
Cross-platform Issues<\/h3>\n
When sharing caches across different environments (e.g., between a local machine and a CI\/CD server), ensure that the environments are compatible. Different OS environments may result in different cached layers, potentially leading to issues when importing. It may be beneficial to use a dedicated build server with a controlled environment.<\/p>\n
Conclusion<\/h2>\n
The Dockerfile<\/a><\/span>A Dockerfile is a script containing a series of instructions to automate the creation of Docker images. It specifies the base image, application dependencies, and configuration, facilitating consistent deployment across environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> --exporter-cache<\/code> option is a valuable tool that can significantly enhance the efficiency of your image<\/a><\/span>Une image est une repr\u00e9sentation visuelle d'un objet ou d'une sc\u00e8ne, g\u00e9n\u00e9ralement compos\u00e9e de pixels dans les formats num\u00e9riques. Elle peut transmettre des informations, susciter des \u00e9motions et faciliter la communication \u00e0 travers diff\u00e9rents m\u00e9dias. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> builds. By understanding how to implement and manage export caches, developers can expedite their workflows, maintain consistency across team members, and optimize CI\/CD processes. As with any powerful tool, careful management, best practices, and awareness of potential pitfalls are essential for maximizing its benefits.<\/p>\n
As the landscape of containerization continues to evolve, features like --exporter-cache<\/code> will play an increasingly vital role in ensuring that developers can build, share, and deploy applications with speed and confidence. By leveraging caching effectively, you can focus more on development and less on waiting, leading to a more productive and satisfying development experience.<\/p>","protected":false},"excerpt":{"rendered":"
The Dockerfile<\/a><\/span>A Dockerfile is a script containing a series of instructions to automate the creation of Docker images. It specifies the base image, application dependencies, and configuration, facilitating consistent deployment across environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> `\u2013export-cache` option enhances build efficiency by allowing developers to save and reuse intermediate build layers. This feature minimizes redundant work, optimizing both time and resource usage during the Docker image<\/a><\/span>Une image est une repr\u00e9sentation visuelle d'un objet ou d'une sc\u00e8ne, g\u00e9n\u00e9ralement compos\u00e9e de pixels dans les formats num\u00e9riques. Elle peut transmettre des informations, susciter des \u00e9motions et faciliter la communication \u00e0 travers diff\u00e9rents m\u00e9dias. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> processus de cr\u00e9ation.<\/p>","protected":false},"author":1,"featured_media":2023,"parent":0,"template":"","glossary-cat":[],"class_list":["post-1355","glossary","type-glossary","status-publish","has-post-thumbnail","hentry"],"yoast_head":"\nDockerfile -export-cache - 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\/fr\/wiki\/dockerfile-export-cache\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Dockerfile -export-cache - Dockerpros\" \/>\n<meta property=\"og:description\" content=\"The Dockerfile `--export-cache` option enhances build efficiency by allowing developers to save and reuse intermediate build layers. This feature minimizes redundant work, optimizing both time and resource usage during the Docker image creation process.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-export-cache\/\" \/>\n<meta property=\"og:site_name\" content=\"Dockerpros\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-export-cache_1355.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=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/\",\"url\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/\",\"name\":\"Dockerfile -export-cache - Dockerpros\",\"isPartOf\":{\"@id\":\"https:\/\/dockerpros.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-export-cache_1355.jpg\",\"datePublished\":\"2024-07-23T12:37:58+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#primaryimage\",\"url\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-export-cache_1355.jpg\",\"contentUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-export-cache_1355.jpg\",\"width\":800,\"height\":600,\"caption\":\"dockerfile-export-cache-2\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#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 –export-cache\"}]},{\"@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\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dockerpros.com\/#organization\",\"name\":\"Dockerpros\",\"url\":\"https:\/\/dockerpros.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@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 -export-cache - Docker pour les pros","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\/fr\/wiki\/dockerfile-export-cache\/","og_locale":"fr_FR","og_type":"article","og_title":"Dockerfile -export-cache - Dockerpros","og_description":"The Dockerfile `--export-cache` option enhances build efficiency by allowing developers to save and reuse intermediate build layers. This feature minimizes redundant work, optimizing both time and resource usage during the Docker image creation process.","og_url":"https:\/\/dockerpros.com\/fr\/wiki\/dockerfile-export-cache\/","og_site_name":"Dockerpros","og_image":[{"width":800,"height":600,"url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-export-cache_1355.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/","url":"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/","name":"Dockerfile -export-cache - Docker pour les pros","isPartOf":{"@id":"https:\/\/dockerpros.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#primaryimage"},"image":{"@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#primaryimage"},"thumbnailUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-export-cache_1355.jpg","datePublished":"2024-07-23T12:37:58+00:00","breadcrumb":{"@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#primaryimage","url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-export-cache_1355.jpg","contentUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/dockerfile-export-cache_1355.jpg","width":800,"height":600,"caption":"dockerfile-export-cache-2"},{"@type":"BreadcrumbList","@id":"https:\/\/dockerpros.com\/wiki\/dockerfile-export-cache\/#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 –export-cache"}]},{"@type":"WebSite","@id":"https:\/\/dockerpros.com\/#website","url":"https:\/\/dockerpros.com\/","name":"Dockerpros","description":"DockerPros \u2013 Votre centre de ressources Docker incontournable","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":"fr-FR"},{"@type":"Organization","@id":"https:\/\/dockerpros.com\/#organization","name":"Dockerpros","url":"https:\/\/dockerpros.com\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@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\/fr\/wp-json\/wp\/v2\/glossary\/1355","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/types\/glossary"}],"author":[{"embeddable":true,"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/glossary\/1355\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/media\/2023"}],"wp:attachment":[{"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/media?parent=1355"}],"wp:term":[{"taxonomy":"glossary-cat","embeddable":true,"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/glossary-cat?post=1355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}