You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That issue is quite verbose and never really presents a closing solution. I did find a reference therein that mentioned network mounted paths do not resolve correctly, so I moved my getting-started environment to an indigenous hard drive and things started working.
My suggestion is that users should be warned early on that using network mapped drives is not supported.
The text was updated successfully, but these errors were encountered:
There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.
Prevent issues from auto-closing with a /lifecycle frozen comment.
File: get-started/06_bind_mounts.md
I was having the troubles mentioned in:
docker/getting-started#76
That issue is quite verbose and never really presents a closing solution. I did find a reference therein that mentioned network mounted paths do not resolve correctly, so I moved my getting-started environment to an indigenous hard drive and things started working.
My suggestion is that users should be warned early on that using network mapped drives is not supported.
The text was updated successfully, but these errors were encountered: