Understanding the /home/user mount #225
-
|
I was looking in to using this container, but I'm a bit confused by the The documentation says "This location contains files from your host that need to be accessible to the application.", but this is a pretty nebulous statement. Which files and why? This seems to be contrary docker's principle of isolating applications. E.g. a typical user's home directory could contain session cookies, ssh keys, or a practically infinite range of other sensitive data that the application ought to be able to be kept isolated from. What if I were to create a new user with an empty (or no) home directory (preferable in the context of server deployment)? Is an empty, read-only directory (effectively a dummy) somehow necessary/acceptable? Any help clearing up this confusion is appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
A practical example of this is MakeMKV that allows you to create MKVs from an ISO file. This ISO file comes from the host and needs to be accessible by MakeMKV. Thus, in this situation, you will map the folder containing your ISOs to the container. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for such quick clarification! |
Beta Was this translation helpful? Give feedback.
/home/useris really just an example. It can be any folder. It doesn't have to be a home folder. The mount is also optional.A practical example of this is MakeMKV that allows you to create MKVs from an ISO file. This ISO file comes from the host and needs to be accessible by MakeMKV. Thus, in this situation, you will map the folder containing your ISOs to the container.