-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Update start.md #22285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update start.md #22285
Conversation
Let the reader know that the executable may not be on the PATH and needs to be manually added
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
* [PS] it may also be that upon installion docker fails to properly added the appropriate executable folders to your paths in this case you would have to find the root installation folder for docker and the following paths to your PATH variable in order to properly access the commands | ||
[ROOT_PATH]/ | ||
[ROOT_PATH]/resources | ||
[ROOT_PATH]/resources/bin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are not standard locations to install the daemon in; I'm not sure if we need to mention such cases.
Do you have more context in what kind of setup dockerd
would be installed in such a location?
Thanks for the pull request. We'd like to make our product docs better, but haven’t been able to review all the suggestions. If the updates are still relevant, review our contribution guidelines and rebase your pull request against the latest version of the docs, then mark it as fresh with a Prevent pull requests from auto-closing with a /lifecycle stale |
Closing for now per my earlier comment |
Greetings we never saw a response to the comment "These are not standard locations to install the daemon in; I'm not sure if we need to mention such cases. Do you have more context in what kind of setup dockerd would be installed in such a location?" its not abaout the daemon its about the docker executables, and there are isntalled here on windows as per our installation |
Let the reader know that the executable may not be on the PATH and needs to be manually added
Description
Added a note to let the user know that they may need to add executable folders to the path and that docker may not do it own its own. I would like to mention that the different executables are in different folders, they should all be in a bin folder in one spot so the end user does not have to added several folders to the PATH variable
Related issues or tickets
Reviews