docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of https://github.com/docker/docker.github.io

This commit is contained in:
John Mulhausen 2016-10-05 16:44:32 -07:00
parent 77c010136b aa183f93fa
commit 626d31eb07
2 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docker-for-windows/faqs.md
View File

@ -130,11 +130,14 @@ does not work](troubleshoot.md#inotify-on-shared-drives-does-not-work) in
### Are symlinks supported?
Docker for Windows supports symbolic links (symlinks) created within containers.
Symbolic link (symlinks) created within containers and across containers will
resolve.
Symlinks created outside of containers (e.g., on the host) will not work in containers.
Symlinks will resolve within and across containers.
Symlinks created elsewhere (e.g., on the host) will not work.
To learn more about the reasons for this limitation, see this issue on GitHub: [Symlinks don't work as expected](https://github.com/docker/for-win/issues/109#issuecomment-251307391).
To learn more about the reasons for this limitation, see the following discussions:
* GitHub issue: [Symlinks don't work as expected](https://github.com/docker/for-win/issues/109#issuecomment-251307391)
* Docker for Windows forums topic: [Symlinks on shared volumes not supported](https://forums.docker.com/t/symlinks-on-shared-volumes-not-supported/9288)
### How do I add custom CA certificates?

4
docker-for-windows/troubleshoot.md
View File

@ -89,6 +89,10 @@ Here is an example of how to de-bug this problem, given a scenario where you sha
See also, the related issue on GitHub, [Mounted volumes are empty in the container](https://github.com/docker/for-win/issues/25).
### Understand symlinks limitations
Symlinks will work within and across containers. However, symlinks created outside of containers (for example, on the host) will not work. To learn more, see [Are symlinks supported?](faqs.md#are-symlinks-supported) in the FAQs.
### Avoid unexpected syntax errors, use Unix style line endings for files in containers
Any file destined to run inside a container must use Unix style `\n` line endings. This includes files referenced at the command line for builds and in RUN commands in Docker files.