{"id":1228,"date":"2024-07-22T20:46:58","date_gmt":"2024-07-22T20:46:58","guid":{"rendered":"https:\/\/dockerpros.com\/?post_type=glossary&p=1228"},"modified":"2024-07-22T20:51:41","modified_gmt":"2024-07-22T20:51:41","slug":"docker-container-update","status":"publish","type":"glossary","link":"https:\/\/dockerpros.com\/fr\/wiki\/docker-container-update\/","title":{"rendered":"Mise \u00e0 jour du conteneur Docker"},"content":{"rendered":"

Advanced Guide to Docker Container Update<\/h1>\n

Docker est une plateforme qui permet aux d\u00e9veloppeurs d'automatiser le d\u00e9ploiement, scaling<\/a><\/span>Scaling refers to the process of adjusting the capacity of a system to accommodate varying loads. It can be achieved through vertical scaling, which enhances existing resources, or horizontal scaling, which adds additional resources. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>, et gestion des applications dans des conteneurs l\u00e9gers et portables. Un Docker conteneur<\/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> encapsule une application et ses d\u00e9pendances dans un seul objet, ce qui facilite son d\u00e9placement et son 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> across various environments. Understanding how to update Docker containers efficiently is crucial for maintaining application performance, security, and reliability. This article delves into advanced techniques for updating Docker containers, exploring best practices, strategies, and tools to ensure seamless updates throughout the conteneur<\/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> lifecycle.<\/p>\n

Comprendre les mises \u00e0 jour des conteneurs Docker<\/h2>\n

Le besoin de mises \u00e0 jour<\/h3>\n

Conteneur<\/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> updates can arise due to numerous reasons, including security vulnerabilities, performance enhancements, or the addition of new features. Updating containers is essential to maintain the integrity and responsiveness of applications while minimizing downtime. Developers face the challenge of ensuring that updates do not disrupt ongoing operations or introduce new issues. Hence, understanding the nuances of conteneur<\/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> updates becomes vital for effective Docker management.<\/p>\n

Strat\u00e9gies de mise \u00e0 jour<\/h3>\n

En ce qui concerne la mise \u00e0 jour des conteneurs Docker, il existe diff\u00e9rentes strat\u00e9gies \u00e0 consid\u00e9rer. Chaque m\u00e9thode pr\u00e9sente ses avantages et ses inconv\u00e9nients, en fonction de l'architecture de l'application, de l'ampleur des changements et des exigences op\u00e9rationnelles. Voici quelques strat\u00e9gies courantes :<\/p>\n

    \n
  1. \n

    In-Place Update<\/strong>: This method involves stopping the existing conteneur<\/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> and replacing it with a new version of the same conteneur<\/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> 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>. Bien que cela soit simple, cela peut entra\u00eener des temps d'arr\u00eat et n\u00e9cessiter une gestion minutieuse des applications avec \u00e9tat.<\/p>\n<\/li>\n

  2. \n

    Rolling Update<\/strong>: Dans cette strat\u00e9gie, les mises \u00e0 jour sont d\u00e9ploy\u00e9es progressivement sur les n\u0153uds d'un cluster. Cette approche permet \u00e0 certaines parties de l'application de rester op\u00e9rationnelles pendant que d'autres sont mises \u00e0 jour, r\u00e9duisant ainsi efficacement les temps d'arr\u00eat et les risques.<\/p>\n<\/li>\n

  3. \n

    D\u00e9ploiement Bleu-Vert<\/strong>: This technique involves maintaining two identical environments (blue and green). One environment runs the current application version, while the other is updated to the new version. After testing the new version, traffic is switched to the updated environment, ensuring a seamless transition.<\/p>\n<\/li>\n

  4. \n

    Canary Release<\/strong>: Similar to blue-green deployments, canary releases involve deploying the new conteneur<\/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> version to a small subset of users. This allows for real-world testing of the update before a full rollout, drastically minimizing potential issues.<\/p>\n<\/li>\n<\/ol>\n

    Versioning et \u00c9tiquetage<\/h3>\n

    To manage updates effectively, versioning and tagging Docker images is crucial. Semantic versioning (SemVer) is a popular approach that uses a three-part version number: MAJOR.MINOR.PATCH. Incrementing these numbers signals the type of changes made. For instance, incrementing the MAJOR version indicates breaking changes, while MINOR and PATCH versions denote backward-compatible improvements and bug fixes, respectively.<\/p>\n

    Using Docker tags, developers can categorize images based on their versions or purpose. For example:<\/p>\n

    docker build -t monapp:1.0.0 .<\/code><\/pre>\n
    This command builds an 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 tags it with version 1.0.0. Tags can also be used for identifying stable releases (e.g., myapp:derni\u00e8re<\/code>) ou des constructions sp\u00e9cifiques (par exemple, myapp:dev<\/code>). Des pratiques de balisage appropri\u00e9es facilitent la gestion et la mise \u00e0 jour des conteneurs en cas de besoin.<\/p>\n
    Updating Containers: Step-by-Step Guide<\/h2>\n
    1. V\u00e9rifier l'\u00e9tat actuel du conteneur<\/h3>\n
    Before proceeding with updates, it\u2019s essential to check the status of your current containers. Use the following command to list running containers:<\/p>\n
    docker ps<\/code><\/pre>\n
    Identify the conteneur<\/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> that requires an update and note its running configuration.<\/p>\n
    2. T\u00e9l\u00e9chargez la derni\u00e8re image<\/h3>\n
    To update a conteneur<\/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>, you typically need the latest version of its 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>. Use the docker pull<\/code> commande pour r\u00e9cup\u00e9rer la version mise \u00e0 jour :<\/p>\n
    docker pull myapp:latest<\/code><\/pre>\n
    This command downloads the latest 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> from the specified repository<\/a><\/span>A repository is a centralized location where data, code, or documents are stored, managed, and maintained. It facilitates version control, collaboration, and efficient resource sharing among users. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span><\/span><\/span>. Si vous utilisez des \u00e9tiquettes versionn\u00e9es, remplacez latest<\/code> avec le num\u00e9ro de version souhait\u00e9.<\/p>\n
    3. Stop the Running Container<\/h3>\n
    Once the latest 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> is available, stop the currently running conteneur<\/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>:<\/p>\n
    docker stop <\/code><\/pre>\n
    Replace “ with the actual ID or name of the conteneur<\/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>. Stopping the conteneur<\/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> gracefully ensures that it has time to complete any ongoing tasks.<\/p>\n
    4. Remove the Old Container<\/h3>\n
    After stopping the conteneur<\/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>, remove it to free up resources:<\/p>\n
    docker rm <\/code><\/pre>\n
    This step is necessary to avoid conflicts with the new conteneur<\/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> instance.<\/p>\n
    5. Run a New Container with the Updated Image<\/h3>\n
    Now, create a new conteneur<\/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> using the updated 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>:<\/p>\n
    docker 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> -d --name myapp_container myapp:latest<\/code><\/pre>\n
    The -d<\/code> flag runs the conteneur<\/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> in detached mode, while --nom<\/code> assigns a name to the new conteneur<\/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> for easier management.<\/p>\n
    6. Verify the Update<\/h3>\n
    After creating the new conteneur<\/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>, check its status to ensure it is running correctly:<\/p>\n
    docker ps<\/code><\/pre>\n
    Also, verify logs and other metrics to confirm that the application is functioning as expected:<\/p>\n
    docker logs myapp_container<\/code><\/pre>\n
    Techniques de mise \u00e0 jour avanc\u00e9es<\/h2>\n
    Bien que la section pr\u00e9c\u00e9dente aborde les bases de la mise \u00e0 jour des conteneurs, il existe des techniques plus avanc\u00e9es qui peuvent am\u00e9liorer l'efficacit\u00e9 et r\u00e9duire les risques.<\/p>\n
    Utilisation de Docker Compose pour les mises \u00e0 jour<\/h3>\n
    Docker Compose<\/a><\/span>Docker Compose is a tool for defining and running multi-container Docker applications using a YAML file. It simplifies deployment, configuration, and orchestration of services, enhancing development efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> is a tool that simplifies the management of multi-container Docker applications. When updating services defined in a docker-compose.yml<\/code> Fichier, vous pouvez utiliser la commande suivante :<\/p>\n
    docker-compose up -d --build<\/code><\/pre>\n
    The --build<\/code> flag ensures that Docker rebuilds the images based on the specified configurations, pulling the latest versions as needed. This approach streamlines the update process, especially for applications composed of multiple interdependent services.<\/p>\n
    Utilisation de Docker Swarm pour les mises \u00e0 jour continues\n\nLes mises \u00e0 jour continues sont une fonctionnalit\u00e9 essentielle de Docker Swarm qui permet de d\u00e9ployer de nouvelles versions d'une application sans temps d'arr\u00eat. Cette fonctionnalit\u00e9 est particuli\u00e8rement utile pour les applications critiques qui n\u00e9cessitent une haute disponibilit\u00e9.\n\nPour illustrer ce concept, prenons l'exemple d'une application web simple compos\u00e9e de deux services : un service frontend et un service backend. Supposons que nous ayons d\u00e9j\u00e0 d\u00e9ploy\u00e9 cette application sur un cluster Docker Swarm et que nous souhaitons maintenant mettre \u00e0 jour le service backend vers une nouvelle version.\n\nPour effectuer une mise \u00e0 jour continue, nous pouvons utiliser la commande `docker service update` avec l'option `--update-parallelism` pour sp\u00e9cifier le nombre de conteneurs \u00e0 mettre \u00e0 jour simultan\u00e9ment. Par exemple, si nous avons 10 r\u00e9plicas du service backend, nous pouvons choisir de mettre \u00e0 jour 2 conteneurs \u00e0 la fois.\n\nVoici un exemple de commande pour effectuer une mise \u00e0 jour continue du service backend :\n\n```\ndocker service update --image mybackend:v2 --update-parallelism 2 backend\n```\n\nDans cet exemple, nous mettons \u00e0 jour le service backend en utilisant l'image `mybackend:v2` et en sp\u00e9cifiant un parall\u00e9lisme de mise \u00e0 jour de 2. Docker Swarm va alors mettre \u00e0 jour 2 conteneurs \u00e0 la fois, en veillant \u00e0 ce que les autres conteneurs continuent de fonctionner normalement.\n\nPendant la mise \u00e0 jour, Docker Swarm surveille l'\u00e9tat de sant\u00e9 des conteneurs mis \u00e0 jour. Si un conteneur ne passe pas les contr\u00f4les de sant\u00e9, Docker Swarm annulera automatiquement la mise \u00e0 jour et restaurera les conteneurs \u00e0 leur \u00e9tat pr\u00e9c\u00e9dent. Cela garantit que l'application reste disponible et fonctionnelle pendant la mise \u00e0 jour.\n\nUne fois la mise \u00e0 jour termin\u00e9e, tous les conteneurs du service backend seront mis \u00e0 jour vers la nouvelle version. Vous pouvez v\u00e9rifier l'\u00e9tat de la mise \u00e0 jour en utilisant la commande `docker service ps backend`.\n\nEn plus du parall\u00e9lisme de mise \u00e0 jour, Docker Swarm offre \u00e9galement d'autres options de configuration pour les mises \u00e0 jour continues, telles que le d\u00e9lai entre les mises \u00e0 jour des conteneurs, le nombre maximum de conteneurs en \u00e9chec autoris\u00e9s, etc. Ces options peuvent \u00eatre sp\u00e9cifi\u00e9es \u00e0 l'aide des options `--update-delay`, `--update-failure-action`, etc.\n\nEn conclusion, les mises \u00e0 jour continues de Docker Swarm permettent de d\u00e9ployer de nouvelles versions d'une application sans temps d'arr\u00eat, en mettant \u00e0 jour les conteneurs de mani\u00e8re contr\u00f4l\u00e9e et en surveillant leur \u00e9tat de sant\u00e9. Cette fonctionnalit\u00e9 est essentielle pour maintenir la disponibilit\u00e9 et la fiabilit\u00e9 des applications critiques dans un environnement de production.<\/h3>\n
    Docker Swarm<\/a><\/span>Docker Swarm est un outil d'orchestration de conteneurs qui permet de g\u00e9rer un cluster de moteurs Docker. Il simplifie la mise \u00e0 l'\u00e9chelle et le d\u00e9ploiement, en assurant haute disponibilit\u00e9 et \u00e9quilibrage de charge entre les services. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> is an orchestration<\/a><\/span>L'orchestration d\u00e9signe la gestion et la coordination automatis\u00e9es de syst\u00e8mes et de services complexes. Elle optimise les processus en int\u00e9grant diverses composantes, en garantissant un fonctionnement efficace et une utilisation optimale des ressources. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> un outil qui permet de g\u00e9rer des clusters de conteneurs Docker. Il offre un support int\u00e9gr\u00e9 pour les mises \u00e0 jour continues, permettant des mises \u00e0 niveau transparentes avec un temps d'arr\u00eat minimal :<\/p>\n
    docker service update<\/a><\/span>La fonctionnalit\u00e9 Docker Service Update permet des mises \u00e0 jour transparentes des services en cours d'ex\u00e9cution dans un cluster Swarm. Elle facilite les mises \u00e0 jour continues, garantissant un temps d'arr\u00eat minimal tout en maintenant la disponibilit\u00e9 et la stabilit\u00e9 du service. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> --image myapp:latest myapp_service<\/code><\/pre>\n
    Cette commande met \u00e0 jour le sp\u00e9cifi\u00e9 service<\/a><\/span>Le service fait r\u00e9f\u00e9rence \u00e0 l'acte de fournir une assistance ou un soutien pour r\u00e9pondre \u00e0 des besoins ou des exigences sp\u00e9cifiques. Dans divers domaines, il englobe le service client, le support technique et les services professionnels, en mettant l'accent sur l'efficacit\u00e9 et la satisfaction de l'utilisateur. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> to use the new 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>, rolling out updates across the cluster in a controlled manner.<\/p>\n
    Implementing Health Checks<\/h3>\n
    To ensure that updated containers are functioning properly, implement health checks within your Docker configurations. Health checks can automatically determine if a conteneur<\/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> is operating as expected, allowing for quick rollbacks if any issues arise. You can define health checks 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> en utilisant le V\u00e9rification de l'\u00e9tat de sant\u00e9<\/a><\/span>HEALTHCHECK est une directive Docker utilis\u00e9e pour surveiller l'\u00e9tat de sant\u00e9 des conteneurs en ex\u00e9cutant des commandes sp\u00e9cifiques \u00e0 des intervalles d\u00e9finis. Elle am\u00e9liore la fiabilit\u00e9 en permettant des red\u00e9marrages automatiques pour les services en \u00e9chec. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span><\/code> instruction :<\/p>\n
    V\u00e9rification de l'\u00e9tat de sant\u00e9<\/a><\/span>HEALTHCHECK est une directive Docker utilis\u00e9e pour surveiller l'\u00e9tat de sant\u00e9 des conteneurs en ex\u00e9cutant des commandes sp\u00e9cifiques \u00e0 des intervalles d\u00e9finis. Elle am\u00e9liore la fiabilit\u00e9 en permettant des red\u00e9marrages automatiques pour les services en \u00e9chec. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> Invite de commandes<\/a><\/span>CMD, or Command Prompt, is a command-line interpreter in Windows operating systems. It allows users to execute commands, automate tasks, and manage system files through a text-based interface. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> curl --fail http:\/\/localhost:8080\/health || exit 1<\/code><\/pre>\n
    This command checks if the application responds correctly. If not, Docker marks the conteneur<\/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> as unhealthy, and you can take appropriate action.<\/p>\n
    Gestion de la persistance des donn\u00e9es<\/h3>\n
    Stateful applications often require careful data management when updating containers. Docker volumes can help maintain data persistence across conteneur<\/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> updates. When defining a volume<\/a><\/span>Volume is a quantitative measure of three-dimensional space occupied by an object or substance, typically expressed in cubic units. It is fundamental in fields such as physics, chemistry, and engineering. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> in your Docker configuration, it will persist data even if the conteneur<\/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> is stopped or removed:<\/p>\n
    docker 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> -d -v app_data:\/data myapp:latest<\/code><\/pre>\n
    Dans cet exemple, app_data<\/code> est un nomm\u00e9 volume<\/a><\/span>Volume is a quantitative measure of three-dimensional space occupied by an object or substance, typically expressed in cubic units. It is fundamental in fields such as physics, chemistry, and engineering. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> that stores application data, ensuring it remains intact through updates.<\/p>\n
    Utilisation de Docker Registry<\/h3>\n
    Pour les \u00e9quipes travaillant avec des images Docker, maintenir un interne Registre Docker<\/a><\/span>A Docker Registry is a storage and distribution system for Docker images. It allows developers to upload, manage, and share container images, facilitating efficient deployment in diverse environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> can streamline the update process. By hosting images internally, you can have more control over versioning, access, and deployment processes. Docker Registry<\/a><\/span>A Docker Registry is a storage and distribution system for Docker images. It allows developers to upload, manage, and share container images, facilitating efficient deployment in diverse environments. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> vous permet de g\u00e9rer et de distribuer vos images de mani\u00e8re s\u00e9curis\u00e9e, ce qui est particuli\u00e8rement utile pour les entreprises.<\/p>\n
    Best Practices for Container Updates<\/h2>\n
    While there are various techniques and tools available, adhering to best practices can help you achieve successful updates with minimal disruption:<\/p>\n
    1. Automatiser le processus de mise \u00e0 jour<\/h3>\n
    Using Continuous Integration\/Continuous Deployment (CI\/CD) pipelines can automate the process of building, testing, and deploying Docker images. Tools like Jenkins, GitLab CI, or GitHub Actions can trigger updates based on code changes, ensuring that the latest version is always deployed.<\/p>\n
    2. Sauvegardez les donn\u00e9es critiques<\/h3>\n
    Before performing updates, ensure that you have backups of critical data and configurations. This practice safeguards against data loss in case the update fails or introduces issues.<\/p>\n
    3. Monitor and Log Performance<\/h3>\n
    Monitoring tools such as Prometheus, Grafana, or ELK Stack<\/a><\/span>Une pile est une structure de donn\u00e9es qui fonctionne selon le principe du dernier entr\u00e9, premier sorti (LIFO), o\u00f9 l'\u00e9l\u00e9ment le plus r\u00e9cemment ajout\u00e9 est le premier \u00e0 \u00eatre retir\u00e9. Elle prend en charge deux op\u00e9rations principales : empiler et d\u00e9piler. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> can help you track conteneur<\/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> performance and identify potential issues post-update. Logging provides insights into errors and behaviors, facilitating quick troubleshooting.<\/p>\n
    4. Testez les mises \u00e0 jour dans les environnements de pr\u00e9production<\/h3>\n
    Before pushing updates to production, thoroughly test them in staging environments. This practice allows you to catch any issues early and ensures the reliability of the new version under actual usage conditions.<\/p>\n
    5. Rollback Mechanisms<\/h3>\n
    Establish rollback mechanisms to revert to the previous conteneur<\/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> version if the update introduces critical issues. Maintaining a history of versioned images makes it easier to perform rollbacks when necessary.<\/p>\n
    Conclusion<\/h2>\n
    Updating Docker containers is a fundamental aspect of managing modern applications. With a variety of strategies, tools, and best practices at your disposal, you can ensure that updates are performed efficiently and with minimal disruption. Understanding the importance of versioning, implementing automated processes, and leveraging orchestration<\/a><\/span>L'orchestration d\u00e9signe la gestion et la coordination automatis\u00e9es de syst\u00e8mes et de services complexes. Elle optimise les processus en int\u00e9grant diverses composantes, en garantissant un fonctionnement efficace et une utilisation optimale des ressources. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> technologies like Docker Swarm<\/a><\/span>Docker Swarm est un outil d'orchestration de conteneurs qui permet de g\u00e9rer un cluster de moteurs Docker. Il simplifie la mise \u00e0 l'\u00e9chelle et le d\u00e9ploiement, en assurant haute disponibilit\u00e9 et \u00e9quilibrage de charge entre les services. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> and Compose can further streamline your conteneur<\/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> update workflow. As you continue to explore the capabilities of Docker, embracing these advanced techniques will empower you to maintain high-performance, secure applications that meet the demands of today\u2019s dynamic environments. <\/p>\n
    In the fast-evolving world of software development, staying updated and maintaining an efficient conteneur<\/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> update lifecycle is not just beneficial\u2014it’s essential for success.<\/p>","protected":false},"excerpt":{"rendered":"
    Docker conteneur<\/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> Les mises \u00e0 jour sont essentielles pour maintenir la s\u00e9curit\u00e9 et les performances d'une application. Des mises \u00e0 jour r\u00e9guli\u00e8res permettent d'appliquer les derni\u00e8res fonctionnalit\u00e9s et correctifs, am\u00e9liorant ainsi la stabilit\u00e9 et la compatibilit\u00e9.<\/p>","protected":false},"author":1,"featured_media":1773,"parent":0,"template":"","glossary-cat":[],"class_list":["post-1228","glossary","type-glossary","status-publish","has-post-thumbnail","hentry"],"yoast_head":"\nDocker Container Update - 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\/docker-container-update\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Docker Container Update - Dockerpros\" \/>\n<meta property=\"og:description\" content=\"Docker container updates are essential for maintaining application security and performance. Regular updates ensure the latest features and patches are applied, enhancing stability and compatibility.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dockerpros.com\/fr\/wiki\/docker-container-update\/\" \/>\n<meta property=\"og:site_name\" content=\"Dockerpros\" \/>\n<meta property=\"article:modified_time\" content=\"2024-07-22T20:51:41+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/docker-container-update_1228.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=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/docker-container-update\/\",\"url\":\"https:\/\/dockerpros.com\/wiki\/docker-container-update\/\",\"name\":\"Docker Container Update - Dockerpros\",\"isPartOf\":{\"@id\":\"https:\/\/dockerpros.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/docker-container-update_1228.jpg\",\"datePublished\":\"2024-07-22T20:46:58+00:00\",\"dateModified\":\"2024-07-22T20:51:41+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dockerpros.com\/wiki\/docker-container-update\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#primaryimage\",\"url\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/docker-container-update_1228.jpg\",\"contentUrl\":\"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/docker-container-update_1228.jpg\",\"width\":800,\"height\":600,\"caption\":\"docker-container-update-2\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#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\":\"Docker Container Update\"}]},{\"@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":"Mise \u00e0 jour du conteneur Docker - Dockerpros\n\nLes conteneurs Docker sont des environnements isol\u00e9s qui permettent d'ex\u00e9cuter des applications de mani\u00e8re coh\u00e9rente sur diff\u00e9rentes plateformes. Cependant, il est parfois n\u00e9cessaire de mettre \u00e0 jour un conteneur existant pour corriger des bugs, ajouter de nouvelles fonctionnalit\u00e9s ou am\u00e9liorer les performances. Dans cet article, nous allons explorer les diff\u00e9rentes m\u00e9thodes pour mettre \u00e0 jour un conteneur Docker.\n\n1. Red\u00e9marrer le conteneur\n\nLa m\u00e9thode la plus simple pour mettre \u00e0 jour un conteneur Docker est de le red\u00e9marrer. Cela permet de recharger les configurations et les d\u00e9pendances du conteneur. Pour red\u00e9marrer un conteneur, utilisez la commande suivante :\n\n```\ndocker restart \n```\n\n2. Reconstruire l'image du conteneur\n\nSi vous avez apport\u00e9 des modifications \u00e0 l'image du conteneur, vous devrez la reconstruire avant de mettre \u00e0 jour le conteneur. Pour reconstruire une image, utilisez la commande suivante :\n\n```\ndocker build -t  .\n```\n\nUne fois l'image reconstruite, vous pouvez mettre \u00e0 jour le conteneur en utilisant la commande suivante :\n\n```\ndocker run -d --name  \n```\n\n3. Utiliser Docker Compose\n\nSi vous utilisez Docker Compose pour g\u00e9rer vos conteneurs, vous pouvez mettre \u00e0 jour un conteneur en modifiant le fichier docker-compose.yml et en ex\u00e9cutant la commande suivante :\n\n```\ndocker-compose up -d\n```\n\nCette commande reconstruira les images et mettra \u00e0 jour les conteneurs en fonction des modifications apport\u00e9es au fichier docker-compose.yml.\n\n4. Utiliser Docker Swarm\n\nSi vous utilisez Docker Swarm pour orchestrer vos conteneurs, vous pouvez mettre \u00e0 jour un service en utilisant la commande suivante :\n\n```\ndocker service update --image  \n```\n\nCette commande mettra \u00e0 jour le service en utilisant la nouvelle image sp\u00e9cifi\u00e9e.\n\n5. Utiliser Kubernetes\n\nSi vous utilisez Kubernetes pour g\u00e9rer vos conteneurs, vous pouvez mettre \u00e0 jour un d\u00e9ploiement en utilisant la commande suivante :\n\n```\nkubectl set image deployment\/ =\n```\n\nCette commande mettra \u00e0 jour le d\u00e9ploiement en utilisant la nouvelle image sp\u00e9cifi\u00e9e.\n\nEn conclusion, il existe plusieurs m\u00e9thodes pour mettre \u00e0 jour un conteneur Docker, en fonction de votre environnement et de vos besoins. Que vous utilisiez Docker Compose, Docker Swarm ou Kubernetes, il est important de suivre les meilleures pratiques pour assurer une mise \u00e0 jour r\u00e9ussie et sans interruption de service.","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\/docker-container-update\/","og_locale":"fr_FR","og_type":"article","og_title":"Docker Container Update - Dockerpros","og_description":"Docker container updates are essential for maintaining application security and performance. Regular updates ensure the latest features and patches are applied, enhancing stability and compatibility.","og_url":"https:\/\/dockerpros.com\/fr\/wiki\/docker-container-update\/","og_site_name":"Dockerpros","article_modified_time":"2024-07-22T20:51:41+00:00","og_image":[{"width":800,"height":600,"url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/docker-container-update_1228.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/dockerpros.com\/wiki\/docker-container-update\/","url":"https:\/\/dockerpros.com\/wiki\/docker-container-update\/","name":"Mise \u00e0 jour du conteneur Docker - Dockerpros\n\nLes conteneurs Docker sont des environnements isol\u00e9s qui permettent d'ex\u00e9cuter des applications de mani\u00e8re coh\u00e9rente sur diff\u00e9rentes plateformes. Cependant, il est parfois n\u00e9cessaire de mettre \u00e0 jour un conteneur existant pour corriger des bugs, ajouter de nouvelles fonctionnalit\u00e9s ou am\u00e9liorer les performances. Dans cet article, nous allons explorer les diff\u00e9rentes m\u00e9thodes pour mettre \u00e0 jour un conteneur Docker.\n\n1. Red\u00e9marrer le conteneur\n\nLa m\u00e9thode la plus simple pour mettre \u00e0 jour un conteneur Docker est de le red\u00e9marrer. Cela permet de recharger les configurations et les d\u00e9pendances du conteneur. Pour red\u00e9marrer un conteneur, utilisez la commande suivante :\n\n```\ndocker restart \n```\n\n2. Reconstruire l'image du conteneur\n\nSi vous avez apport\u00e9 des modifications \u00e0 l'image du conteneur, vous devrez la reconstruire avant de mettre \u00e0 jour le conteneur. Pour reconstruire une image, utilisez la commande suivante :\n\n```\ndocker build -t  .\n```\n\nUne fois l'image reconstruite, vous pouvez mettre \u00e0 jour le conteneur en utilisant la commande suivante :\n\n```\ndocker run -d --name  \n```\n\n3. Utiliser Docker Compose\n\nSi vous utilisez Docker Compose pour g\u00e9rer vos conteneurs, vous pouvez mettre \u00e0 jour un conteneur en modifiant le fichier docker-compose.yml et en ex\u00e9cutant la commande suivante :\n\n```\ndocker-compose up -d\n```\n\nCette commande reconstruira les images et mettra \u00e0 jour les conteneurs en fonction des modifications apport\u00e9es au fichier docker-compose.yml.\n\n4. Utiliser Docker Swarm\n\nSi vous utilisez Docker Swarm pour orchestrer vos conteneurs, vous pouvez mettre \u00e0 jour un service en utilisant la commande suivante :\n\n```\ndocker service update --image  \n```\n\nCette commande mettra \u00e0 jour le service en utilisant la nouvelle image sp\u00e9cifi\u00e9e.\n\n5. Utiliser Kubernetes\n\nSi vous utilisez Kubernetes pour g\u00e9rer vos conteneurs, vous pouvez mettre \u00e0 jour un d\u00e9ploiement en utilisant la commande suivante :\n\n```\nkubectl set image deployment\/ =\n```\n\nCette commande mettra \u00e0 jour le d\u00e9ploiement en utilisant la nouvelle image sp\u00e9cifi\u00e9e.\n\nEn conclusion, il existe plusieurs m\u00e9thodes pour mettre \u00e0 jour un conteneur Docker, en fonction de votre environnement et de vos besoins. Que vous utilisiez Docker Compose, Docker Swarm ou Kubernetes, il est important de suivre les meilleures pratiques pour assurer une mise \u00e0 jour r\u00e9ussie et sans interruption de service.","isPartOf":{"@id":"https:\/\/dockerpros.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#primaryimage"},"image":{"@id":"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#primaryimage"},"thumbnailUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/docker-container-update_1228.jpg","datePublished":"2024-07-22T20:46:58+00:00","dateModified":"2024-07-22T20:51:41+00:00","breadcrumb":{"@id":"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dockerpros.com\/wiki\/docker-container-update\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#primaryimage","url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/docker-container-update_1228.jpg","contentUrl":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/docker-container-update_1228.jpg","width":800,"height":600,"caption":"docker-container-update-2"},{"@type":"BreadcrumbList","@id":"https:\/\/dockerpros.com\/wiki\/docker-container-update\/#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":"Docker Container Update"}]},{"@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\/1228","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\/1228\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/media\/1773"}],"wp:attachment":[{"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/media?parent=1228"}],"wp:term":[{"taxonomy":"glossary-cat","embeddable":true,"href":"https:\/\/dockerpros.com\/fr\/wp-json\/wp\/v2\/glossary-cat?post=1228"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}