Skip to content

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

Closed
wants to merge 1 commit into from
Closed

Update start.md #22285

wants to merge 1 commit into from

Conversation

windmillcode0
Copy link

@windmillcode0 windmillcode0 commented Mar 20, 2025

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

  • Technical review
  • Editorial review
  • Product review

Let the reader know that the executable may not be on the PATH and needs to be manually added
@github-actions github-actions bot added the area/engine Issue affects Docker engine/daemon label Mar 20, 2025
Copy link

netlify bot commented Mar 20, 2025

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 5b65ca1
🔍 Latest deploy log https://app.netlify.com/sites/docsdocker/deploys/67dc2f07bc73390008185845
😎 Deploy Preview https://deploy-preview-22285--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Comment on lines +52 to +56

* [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
Copy link
Member

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?

@docker-robot
Copy link

docker-robot bot commented Jun 18, 2025

Thanks for the pull request. We'd like to make our product docs better, but haven’t been able to review all the suggestions.
As our docs have also diverged, we do not have the bandwidth to review and rebase old pull requests.

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 /remove-lifecycle stale comment.
If not, this pull request will be closed in 30 days. This helps our maintainers focus on the active pull requests.

Prevent pull requests from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

@thaJeztah
Copy link
Member

Closing for now per my earlier comment

@thaJeztah thaJeztah closed this Jun 18, 2025
@windmillcode0
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/engine Issue affects Docker engine/daemon lifecycle/stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants