Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung |
| modul:m347:learningunits:lu05:lu05a [2025/03/07 11:58] – dgaravaldi | modul:m347:learningunits:lu05:lu05a [2025/06/03 16:57] (aktuell) – dgaravaldi |
|---|
| |
| === Volumes === | === Volumes === |
| Most commonly used storage type is called a ''volume''. In a ''volume'', the container storage is completely isolated from the host file system. Although the data of ''volume'' is sorted in a specific directory of the host, they are controlled and managed by docker command line. Compared to other options of storage which we will visit soon enough, ''volume''s are more secure to ship and more reliable to operate. | Most commonly used storage type is called a ''volume''. In a ''volume'', the container storage is completely isolated from the host file system. Although the data of ''volume'' is sorted in a specific directory of the host, they are controlled and managed by docker command line. Compared to other options of storage which we will visit soon enough, ''volumes'' are more secure to ship and more reliable to operate. |
| <br''Volumes'' are storage objects of docker which are mounted to containers. In terms of implementation, ''volumes'' are dedicated directories on hosts file system. If a containerized app is shipped along with the ''volume'', people apart from the developer himself using the app will end up creating such a directory on their own docker hosts. | ''Volumes'' are storage objects of docker which are mounted to containers. In terms of implementation, ''volumes'' are dedicated directories on hosts file system. If a containerized app is shipped along with the ''volume'', people apart from the developer himself using the app will end up creating such a directory on their own docker hosts. |
| |
| |