Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 51.1
edited by Erik Bakker
on 2022/12/29 12:33
Change comment: There is no comment for this version
To version 49.1
edited by Erik Bakker
on 2022/10/31 15:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  
3 -{{warning}}
4 -Please note that this microlearning is for the new monitoring stack only.
5 -{{/warning}}
6 -
7 7  When you need to read and write files from an on-premise disk, you need to know the path in which the data is stored and make sure that the docker container in your runtime(s) running has access to this path. There are several ways of dealing with this challenge. First, this microlearning will discuss the various alternatives and best approaches in these scenarios.
8 8  
9 9  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
... ... @@ -72,9 +72,7 @@
72 72  
73 73  To configure a "Bind mount," you need to define a source and a target directory linked to each other. The source directory represents the directory on your local system (that might already be used currently to exchange files). The target directory defines a directory on your docker installation that the runtime can access.
74 74  
75 -{{warning}}Note that when the source directory does not exist, the runtimes cannot be deployed correctly. One of the following two configurations displayed below are needed to find the source directory:
76 -* /mnt/host/{local-directory}
77 -* /run/desktop/mnt/host/{local-directory}{{/warning}}
71 +{{warning}}Note that when the source directory does not exist, the runtimes cannot be deployed correctly.{{/warning}}
78 78  
79 79  [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount-filled-in.png]]
80 80