Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 66.1
edited by Danniar Firdausy
on 2023/11/27 08:38
Change comment: There is no comment for this version
To version 68.1
edited by Erik Bakker
on 2024/03/05 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,9 +1,4 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
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 ensure that the docker container in your runtime(s) running has access to this path. There are several ways of dealing with this challenge. 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]].
... ... @@ -113,6 +113,8 @@
113 113  
114 114  === 3.3 Temporary file system ===
115 115  
111 +{{info}}This option is only relevant when running on Linux.{{/info}}
112 +
116 116  The temporary file system option is for you if you do not want to work with **persistent** data but require **non-persistent** data. This way, you can increase the container's performance by avoiding writing into the container's writable layer.
117 117  
118 118  [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]]
... ... @@ -126,6 +126,10 @@
126 126  
127 127  === 3.4 Named pipe ===
128 128  
126 +{{info}}This option is only relevant when running on Windows.{{/info}}
127 +
128 +A named pipe is a named, one-way or duplex pipe for communication between the pipe server and one or more pipe clients. All instances of a named pipe share the same pipe name, but each instance has its own buffers and handles, and provides a separate conduit for client/server communication. Any process can access named pipes, subject to security checks, making named pipes an easy form of communication between related or unrelated processes.
129 +
129 129  *The named pipe option can be selected, but we yet have to see a valid use case within the context of eMagiz for using this option. Therefore, we won't discuss this option further in this microlearning.
130 130  
131 131  {{warning}}