How to configure OTLP CORS in docker container

[dirthsj]

I'm using the following compose.yml:

services:
  logs:
    image: jaegertracing/all-in-one:latest
    environment:
      - COLLECTOR_OTLP_ENABLED=true
      - COLLECTOR_OTLP_HTTP_CORS_ALLOWED_ORIGINS=*
    ports:
      - 16686:16686 # web ui
      - 4317:4317   # OTLP (gRPC)
      - 4318:4318   # OTLP (http)

with docker compose up

Which I believe should allow all origins using CORS. However, I still get CORS errors when attempting to POST to the OTLP endpoint in the browser.

[yurishkuro]

did you check what latest tag means to your Docker setup? Maybe it's using old version.

[dirthsj]

docker images --digests shows

docker images jaegertracing/all-in-one --digests
REPOSITORY                 TAG       DIGEST                                                                    IMAGE ID       CREATED        SIZE
jaegertracing/all-in-one   latest    sha256:2995e54430c3b3bd9cfeb5c5758fb9edf2ace963a0bfa4a1eec803f427c93dd4   2113c30dad61   18 hours ago   60.3MB

If I use docker compose exec -it logs /bin/sh to enter the container while it is running & run the version command, I get

/go/bin # ./all-in-one-linux version
2023/08/20 18:32:55 maxprocs: Leaving GOMAXPROCS=16: CPU quota undefined
{"gitCommit":"b355fe79428f169293afe8bb6077749f8769bf6a","gitVersion":"v1.48.0","buildDate":"2023-08-19T23:58:29Z"}

[dirthsj]

Turns out, I had the wrong OTLP import. I was importing the OTLPTraceExporter from @opentelemetry/exporter-trace-otlp-grpc not @opentelemetry/exporter-trace-otlp-http. After fixing this, the request no longer has CORS issues and instead stalls indefinitely.

Using @opentelemetry/sdk-node version 0.41.2

I think this might be something weird with Chrome, since if I right click on the request and copy it as a CURL command, the request does succeed and the traces show up as I would expect in jaeger. I'll experiment a bit more.