docs: Add HTTP port to collector docker command

[kaylareopelle]

The docker run command includes a port for GRPC. If someone is using an HTTP OTLP exporter along with the collector, this command will not work out of the box.

This commit adds the HTTP port to the docker run command.

Discovered by @wsmoak in a discussion on: open-telemetry/opentelemetry-ruby#1525 (comment)

[tiffany76]

LGTM. @open-telemetry/collector-approvers, PTAL. Thanks.

[codeboten]

i think the comment here will cause problems

[codeboten]

$ docker run \
     -p 127.0.0.1:4317:4317 \ # for gRPC
     -p 127.0.0.1:4318:4318 \ # for HTTP
     -p 127.0.0.1:55679:55679 \
     otel/opentelemetry-collector-contrib
docker: invalid reference format.
See 'docker run --help'.
zsh: command not found: -p
zsh: command not found: -p

[codeboten]

tried in bash as well to make sure

bash-3.2$ docker run \ -p 127.0.0.1:4317:4317 \ # for gRPC -p 127.0.0.1:4318:4318 \ # for HTTP -p 127.0.0.1:55679:55679 \ otel/opentelemetry-collector-contrib
docker: invalid reference format.
See 'docker run --help'.

[chalin]

Thanks for this addition @kaylareopelle.

@codeboten, right, I'm not surprised that we can't have comments after end of line continuation characters.

All: this being a quick start, I'd suggest just dropping the port-use comments.

[codeboten]

All: this being a quick start, I'd suggest just dropping the port-use comments.

Or even just above the docker run command:

```sh
   # 4317 for gRPC, 4318 for HTTP, 55679 for...
   docker run \
     -p 127.0.0.1:4317:4317 \

[kaylareopelle]

All: this being a quick start, I'd suggest just dropping the port-use comments.

Or even just above the docker run command:

```sh
   # 4317 for gRPC, 4318 for HTTP, 55679 for...
   docker run \
     -p 127.0.0.1:4317:4317 \

Great point, @codeboten! My bad for not testing the snippet with the comments before opening this PR.

I updated the docs to place the comment at the top in 0b0a0d4. However, I'm also open to removing it entirely.

Please take another look when you have a chance!

[chalin]

I still feel it better to just drop the comment, but will let other @open-telemetry/docs-approvers chime in. If we keep it, let's be clear that this comment is referring to port numbers.

[svrnm]

Can we move that comment into the text above, like "Launch the Collector, listening on ports 4317 (for OTLP grPC), 4318 (for OTLP HTTP) and 55679 (for ZPages):"

[kaylareopelle]

Either way works for me! I updated the PR to use the text @svrnm suggested in: c9d08a4

[kaylareopelle]

I don't really understand what the Files / FILE FORMAT (pull_request) check is looking for. What needs to be changed to get it to pass?

[tiffany76]

/fix:format

[opentelemetrybot]

You triggered fix:format action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/11694711177

[opentelemetrybot]

fix:format was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[tiffany76]

Hi @kaylareopelle. The file formatting check flagged the line length: our linter looks for 80 characters per line. I've fixed it with a GitHub action. You should be all set now.

[kaylareopelle]

@chalin - Could you take another look? Since you requested changes, I need your approval before we can move forward.

[chalin]

Thanks for the ping.
LGTM ✨