{"id":700,"date":"2024-07-22T20:38:00","date_gmt":"2024-07-22T20:38:00","guid":{"rendered":"https:\/\/dockerpros.com\/?post_type=glossary&p=700"},"modified":"2024-07-22T20:55:17","modified_gmt":"2024-07-22T20:55:17","slug":"bind-mount","status":"publish","type":"glossary","link":"https:\/\/dockerpros.com\/fr\/wiki\/bind-mount\/","title":{"rendered":"Montage bind"},"content":{"rendered":"

Compr\u00e9hension avanc\u00e9e des bind mounts dans Docker\n\nLes bind mounts sont une fonctionnalit\u00e9 puissante de Docker qui permet de monter des r\u00e9pertoires ou des fichiers de l'h\u00f4te dans un conteneur. Contrairement aux volumes, qui sont g\u00e9r\u00e9s par Docker, les bind mounts utilisent directement le syst\u00e8me de fichiers de l'h\u00f4te. Cela offre une plus grande flexibilit\u00e9, mais n\u00e9cessite \u00e9galement une compr\u00e9hension approfondie de leur fonctionnement.\n\nDans cette section, nous allons explorer les bind mounts en d\u00e9tail, en commen\u00e7ant par leur d\u00e9finition et leur utilisation de base, puis en passant \u00e0 des sc\u00e9narios plus avanc\u00e9s.\n\nD\u00e9finition et utilisation de base\n\nUn bind mount est une mani\u00e8re de monter un r\u00e9pertoire ou un fichier de l'h\u00f4te dans un conteneur. Contrairement aux volumes, qui sont g\u00e9r\u00e9s par Docker, les bind mounts utilisent directement le syst\u00e8me de fichiers de l'h\u00f4te. Cela signifie que les modifications apport\u00e9es aux fichiers dans le conteneur seront refl\u00e9t\u00e9es sur l'h\u00f4te, et vice versa.\n\nPour cr\u00e9er un bind mount, vous pouvez utiliser l'option -v ou --mount lors de l'ex\u00e9cution d'un conteneur. Par exemple, pour monter le r\u00e9pertoire \/data de l'h\u00f4te dans le conteneur \u00e0 l'emplacement \/app, vous pouvez utiliser la commande suivante :\n\n```\ndocker run -v \/data:\/app my_image\n```\n\nOu, en utilisant l'option --mount :\n\n```\ndocker run --mount type=bind,source=\/data,target=\/app my_image\n```\n\nDans les deux cas, le r\u00e9pertoire \/data de l'h\u00f4te sera mont\u00e9 dans le conteneur \u00e0 l'emplacement \/app.\n\nSc\u00e9narios avanc\u00e9s\n\nLes bind mounts peuvent \u00eatre utilis\u00e9s dans des sc\u00e9narios plus avanc\u00e9s, tels que :\n\n1. Montage de fichiers sp\u00e9cifiques : Au lieu de monter un r\u00e9pertoire entier, vous pouvez monter un fichier sp\u00e9cifique de l'h\u00f4te dans le conteneur. Par exemple, pour monter le fichier \/etc\/hosts de l'h\u00f4te dans le conteneur \u00e0 l'emplacement \/etc\/hosts, vous pouvez utiliser la commande suivante :\n\n```\ndocker run -v \/etc\/hosts:\/etc\/hosts my_image\n```\n\n2. Montage en lecture seule : Par d\u00e9faut, les bind mounts sont mont\u00e9s en lecture-\u00e9criture. Cependant, vous pouvez les monter en lecture seule en ajoutant l'option :ro \u00e0 la fin du chemin de montage. Par exemple, pour monter le r\u00e9pertoire \/data de l'h\u00f4te en lecture seule dans le conteneur \u00e0 l'emplacement \/app, vous pouvez utiliser la commande suivante :\n\n```\ndocker run -v \/data:\/app:ro my_image\n```\n\n3. Montage de plusieurs r\u00e9pertoires : Vous pouvez monter plusieurs r\u00e9pertoires ou fichiers de l'h\u00f4te dans un conteneur en utilisant plusieurs options -v ou --mount. Par exemple, pour monter les r\u00e9pertoires \/data et \/config de l'h\u00f4te dans le conteneur \u00e0 l'emplacement \/app et \/etc\/config respectivement, vous pouvez utiliser la commande suivante :\n\n```\ndocker run -v \/data:\/app -v \/config:\/etc\/config my_image\n```\n\n4. Montage de r\u00e9pertoires temporaires : Vous pouvez monter un r\u00e9pertoire temporaire de l'h\u00f4te dans un conteneur en utilisant le r\u00e9pertoire \/tmp. Par exemple, pour monter le r\u00e9pertoire \/tmp\/data de l'h\u00f4te dans le conteneur \u00e0 l'emplacement \/app, vous pouvez utiliser la commande suivante :\n\n```\ndocker run -v \/tmp\/data:\/app my_image\n```\n\n5. Montage de r\u00e9pertoires r\u00e9seau : Vous pouvez monter un r\u00e9pertoire r\u00e9seau de l'h\u00f4te dans un conteneur en utilisant un syst\u00e8me de fichiers r\u00e9seau tel que NFS ou SMB. Par exemple, pour monter le r\u00e9pertoire r\u00e9seau \/net\/data de l'h\u00f4te dans le conteneur \u00e0 l'emplacement \/app, vous pouvez utiliser la commande suivante :\n\n```\ndocker run -v \/net\/data:\/app my_image\n```\n\nConclusion\n\nLes bind mounts sont une fonctionnalit\u00e9 puissante de Docker qui permet de monter des r\u00e9pertoires ou des fichiers de l'h\u00f4te dans un conteneur. Ils offrent une plus grande flexibilit\u00e9 que les volumes, mais n\u00e9cessitent \u00e9galement une compr\u00e9hension approfondie de leur fonctionnement. Dans cette section, nous avons explor\u00e9 les bind mounts en d\u00e9tail, en commen\u00e7ant par leur d\u00e9finition et leur utilisation de base, puis en passant \u00e0 des sc\u00e9narios plus avanc\u00e9s.<\/h1>\n

Docker a r\u00e9volutionn\u00e9 la fa\u00e7on dont les d\u00e9veloppeurs construisent, exp\u00e9dient et 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> applications, primarily through its containerization technology. At the heart of this technology lies a phenomenon known as Montages bind<\/em>. In the simplest terms, a Bind Mount in Docker is a type of 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 allows you to map a specific file or directory from the host system into 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>. This mechanism enables seamless data sharing between the host and 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>, facilitating persistent storage and development workflows. Understanding Bind Mounts goes beyond the basics; it involves exploring their features, advantages, limitations, and best practices for various use cases.<\/p>\n

L'anatomie d'un montage bind<\/h2>\n

Fonctionnement des montages li\u00e9s<\/h3>\n

A Bind Mount operates on a fundamental principle: it links a directory or file on the host system to a directory or file in 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>. This linkage occurs directly in the underlying filesystem, allowing 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> to access and modify the host’s data in real-time. When a Bind Mount is created, any changes made in the directory or file within 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> are reflected immediately on the host and vice versa. <\/p>\n

La commande pour cr\u00e9er un montage bind ressemble g\u00e9n\u00e9ralement \u00e0 ceci :<\/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> -v \/path\/on\/host:\/path\/in\/container <\/code><\/pre>\n
Dans cette commande, \/path\/on\/host<\/code> is the directory on the host machine, while \/path\/in\/container<\/code> is the destination path inside 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>. This approach is particularly useful for development environments where code changes need to be tested immediately without rebuilding 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>.<\/p>\n
Types of Mounts in Docker<\/h3>\n
Avant d'approfondir les Bind Mounts, il est essentiel de conna\u00eetre les autres options disponibles pour g\u00e9rer les donn\u00e9es persistantes dans Docker :<\/p>\n
    \n
  1. \n
    Volumes<\/strong>: G\u00e9r\u00e9s par Docker, ils sont stock\u00e9s dans une partie du syst\u00e8me de fichiers h\u00f4te qui est g\u00e9r\u00e9e par Docker d\u00e9mon<\/a><\/span>Un d\u00e9mon est un processus d'arri\u00e8re-plan en informatique qui s'ex\u00e9cute de mani\u00e8re autonome, effectuant des t\u00e2ches sans intervention de l'utilisateur. Il g\u00e8re g\u00e9n\u00e9ralement des fonctions au niveau du syst\u00e8me ou de l'application, am\u00e9liorant ainsi l'efficacit\u00e9. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>. Volumes are the preferred mechanism for persisting data because they are portable and can be easily shared among containers.<\/p>\n<\/li>\n
  2. \n
    Montages bind<\/strong>: As described, these directly link a host file or directory to 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>. They provide a straightforward way to access host files from within 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> but do not have the same level of manageability as volumes.<\/p>\n<\/li>\n
  3. \n
    tmpfs<\/strong>: This type of mount is stored in the host system\u2019s memory, providing a temporary filesystem for containers. It is ideal for sensitive data that doesn’t need to persist after 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> arr\u00eats.<\/p>\n<\/li>\n<\/ol>\n
    Use Cases for Bind Mounts<\/h3>\n
    Bind Mounts have several practical applications. Here are some common scenarios where they are particularly beneficial:<\/p>\n
      \n
    1. \n
      Development Environments<\/strong>: Developers often use Bind Mounts to connect their local source code directories directly to 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>. This allows for real-time code updates without the need to rebuild 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>.<\/p>\n<\/li>\n
    2. \n
      Gestion de configuration<\/strong>: You can bind mount configuration files into 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>, ensuring that the application uses the latest configuration without needing to alter 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>.<\/p>\n<\/li>\n
    3. \n
      Logging and Data Processing<\/strong>: When containers generate logs or output data, Bind Mounts can be used to direct this data into specific directories on the host, making it easier to access and analyze.<\/p>\n<\/li>\n
    4. \n
      Acc\u00e8s aux fichiers partag\u00e9s<\/strong>: In multi-container applications, Bind Mounts can be used to enable shared access to files among different containers, allowing for collaborative workflows.<\/p>\n<\/li>\n<\/ol>\n
      Advantages of Using Bind Mounts<\/h2>\n
      Flexibility and Speed<\/h3>\n
      L'un des principaux avantages de l'utilisation des montages de liaison est leur flexibilit\u00e9. Les d\u00e9veloppeurs peuvent rapidement it\u00e9rer \u00e0 travers les changements de code sans la surcharge de cr\u00e9ation et de gestion des images Docker. Cette rapidit\u00e9 est cruciale dans les environnements de d\u00e9veloppement et de test o\u00f9 des cycles de r\u00e9troaction rapides sont essentiels.<\/p>\n
      Real-Time Synchronization<\/h3>\n
      Because Bind Mounts create a direct link between the host and 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>, any changes made on either side are reflected immediately. This real-time synchronization is especially useful when working with files that require constant updates or configuration changes.<\/p>\n
      Acc\u00e8s direct aux fichiers h\u00f4te<\/h3>\n
      Les montages li\u00e9s permettent aux conteneurs d'acc\u00e9der et de modifier directement le syst\u00e8me de fichiers de l'h\u00f4te. Cette fonctionnalit\u00e9 est particuli\u00e8rement utile lorsque vous devez travailler avec des donn\u00e9es existantes, des fichiers de configuration ou toute autre ressource situ\u00e9e sur l'h\u00f4te.<\/p>\n
      Limitations des montages li\u00e9s\n\nLes montages li\u00e9s sont un moyen simple de monter des volumes dans Docker, mais ils pr\u00e9sentent certaines limitations importantes :\n\n1. **Performance** : Les montages li\u00e9s peuvent \u00eatre plus lents que les volumes Docker natifs, surtout sur les syst\u00e8mes de fichiers r\u00e9seau.\n\n2. **Portabilit\u00e9** : Les montages li\u00e9s sont li\u00e9s \u00e0 la structure de r\u00e9pertoires de l'h\u00f4te, ce qui peut poser des probl\u00e8mes de portabilit\u00e9 entre diff\u00e9rents environnements.\n\n3. **Permissions** : La gestion des permissions peut \u00eatre complexe, car elle d\u00e9pend du syst\u00e8me de fichiers de l'h\u00f4te.\n\n4. **S\u00e9curit\u00e9** : Les montages li\u00e9s peuvent exposer des donn\u00e9es sensibles si le chemin du r\u00e9pertoire h\u00f4te n'est pas correctement s\u00e9curis\u00e9.\n\n5. **Gestion des versions** : Contrairement aux volumes Docker, les montages li\u00e9s ne b\u00e9n\u00e9ficient pas de la gestion des versions int\u00e9gr\u00e9e de Docker.\n\n6. **Isolation** : Les montages li\u00e9s offrent moins d'isolation que les volumes Docker, car ils sont directement li\u00e9s au syst\u00e8me de fichiers de l'h\u00f4te.\n\n7. **Sauvegarde et restauration** : La sauvegarde et la restauration des donn\u00e9es peuvent \u00eatre plus complexes avec les montages li\u00e9s, car elles d\u00e9pendent du syst\u00e8me de fichiers de l'h\u00f4te.\n\n8. **\u00c9volutivit\u00e9** : Les montages li\u00e9s peuvent ne pas \u00eatre adapt\u00e9s aux environnements hautement \u00e9volutifs, car ils sont li\u00e9s \u00e0 une instance sp\u00e9cifique de l'h\u00f4te.\n\n9. **Concurrence** : Dans les environnements multi-utilisateurs, les montages li\u00e9s peuvent entra\u00eener des conflits de permissions et d'acc\u00e8s.\n\n10. **D\u00e9bogage** : Le d\u00e9bogage des probl\u00e8mes li\u00e9s aux montages li\u00e9s peut \u00eatre plus difficile, car il faut prendre en compte \u00e0 la fois le conteneur et le syst\u00e8me de fichiers de l'h\u00f4te.\n\nEn r\u00e9sum\u00e9, bien que les montages li\u00e9s soient utiles dans certains sc\u00e9narios, ils pr\u00e9sentent des limitations significatives qui doivent \u00eatre prises en compte lors de la conception d'une architecture Docker.<\/h2>\n
      Portability Issues<\/h3>\n
      While Bind Mounts provide flexibility, they can lead to portability issues. Since they depend on specific paths on the host filesystem, moving the application to a different environment can require additional configuration. This limitation is in contrast to Docker Volumes, which are more portable and managed by Docker.<\/p>\n
      Pr\u00e9occupations de s\u00e9curit\u00e9<\/h3>\n
      Bind Mounts can pose security risks, especially when sensitive data is exposed to containers. 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 compromised, an attacker could potentially access sensitive information on the host filesystem. Developers should always assess the security implications when using Bind Mounts.<\/p>\n
      Surcharges de performance<\/h3>\n
      In some cases, Bind Mounts can introduce performance overheads, particularly when dealing with high I\/O workloads. The direct linkage between the host and 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> might cause latency or other performance-related issues, particularly under heavy load.<\/p>\n
      Meilleures pratiques pour l'utilisation des montages de liaison<\/h2>\n
      D\u00e9finir des cas d'utilisation clairs<\/h3>\n
      Avant de mettre en \u0153uvre les Bind Mounts, d\u00e9finissez clairement les cas d'utilisation pour leur application. Comprenez si les avantages l'emportent sur les limitations dans votre contexte sp\u00e9cifique, en particulier dans les environnements de production.<\/p>\n
      Use Absolute Paths<\/h3>\n
      Always use absolute paths when specifying Bind Mounts. Relative paths can lead to confusion and errors, particularly when running containers from different working directories.<\/p>\n
      Limit Bind Mount Permissions<\/h3>\n
      To mitigate security risks, it is best practice to limit the permissions of the files and directories being mounted. Ensure that only the necessary permissions are granted, reducing the risk of unauthorized access.<\/p>\n
      Monitor Performance<\/h3>\n
      Si vous utilisez des Bind Mounts dans une application sensible aux performances, surveillez de pr\u00e8s les performances de l'application. Utilisez les outils de surveillance int\u00e9gr\u00e9s de Docker ou des solutions tierces pour d\u00e9celer les goulots d'\u00e9tranglement ou probl\u00e8mes li\u00e9s aux performances d'E\/S.<\/p>\n
      Consider Alternatives<\/h3>\n
      Dans la mesure du possible, \u00e9valuez si les Volumes Docker pourraient \u00eatre une alternative plus appropri\u00e9e pour votre cas d'utilisation. Bien que les Bind Mounts soient excellents pour les environnements de d\u00e9veloppement, les Volumes peuvent offrir une meilleure portabilit\u00e9, gestion et s\u00e9curit\u00e9.<\/p>\n
      Real-World Examples of Bind Mounts<\/h2>\n
      Exemple 1 : Environnement de d\u00e9veloppement local<\/h3>\n
      Disons que vous d\u00e9veloppez une application web en utilisant Node<\/a><\/span>Node, or Node.js, is a JavaScript runtime built on Chrome's V8 engine, enabling server-side scripting. It allows developers to build scalable network applications using asynchronous, event-driven architecture. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>.js. You want to bind your local project directory to 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> to enable real-time updates:<\/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> -v \/path\/to\/your\/project:\/app -w \/app 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>:latest npm start<\/code><\/pre>\n
      In this command:<\/p>\n