-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[DOCS] Remove extra ports in Docker command #91118
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
Conversation
The current command to start the first Elasticsearch node includes `-p 9200:9200` and `-p 9300:9300`. This PR removes the extra ports so that they're not open unnecessarily.
|
Documentation preview: |
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-delivery (Team:Delivery) |
bytebilly
left a comment
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.
Are we sure that the port is not required to get other nodes enrolled later? I'd love to be sure that the end-to-end documented flow still works, has this been tested after the change?
@bytebilly, I tested the documentation without the |
|
@lockewritesdocs please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
The current command to start the first Elasticsearch node includes `-p 9200:9200` and `-p 9300:9300`. This PR removes the extra ports so that they're not open unnecessarily. Co-authored-by: Adam Locke <[email protected]>
The current command to start the first Elasticsearch node includes `-p 9200:9200` and `-p 9300:9300`. This PR removes the extra ports so that they're not open unnecessarily. Co-authored-by: Adam Locke <[email protected]>
The current command to start the first Elasticsearch node includes `-p 9200:9200` and `-p 9300:9300`. This PR removes the extra ports so that they're not open unnecessarily. Co-authored-by: Adam Locke <[email protected]>
The current command to start the first Elasticsearch node includes `-p 9200:9200` and `-p 9300:9300`. This PR removes the extra ports so that they're not open unnecessarily. Co-authored-by: Adam Locke <[email protected]> Co-authored-by: Adam Locke <[email protected]> Co-authored-by: Adam Locke <[email protected]>
The current command to start the first Elasticsearch node includes `-p 9200:9200` and `-p 9300:9300`. This PR removes the extra ports so that they're not open unnecessarily. Co-authored-by: Adam Locke <[email protected]> Co-authored-by: Adam Locke <[email protected]> Co-authored-by: Adam Locke <[email protected]>
The current command to start the first Elasticsearch node includes `-p 9200:9200` and `-p 9300:9300`. This PR removes the extra ports so that they're not open unnecessarily. Co-authored-by: Adam Locke <[email protected]> Co-authored-by: Adam Locke <[email protected]> Co-authored-by: Adam Locke <[email protected]>
The current command to start the first Elasticsearch node includes `-p 9200:9200` and `-p 9300:9300`. This PR removes the extra ports so that they're not open unnecessarily. Co-authored-by: Adam Locke <[email protected]>
The current command to start the first Elasticsearch node includes
-p 9200:9200and-p 9300:9300. This PR removes the extra ports so that they're not open unnecessarily.