docker
[BUG] OTel version conflict from moby/buildkit package
Description
I use testcontainers. And there was a need to use docker-compose, which contains a service that runs through dockerfile. An error appears in opentelemetry at startup
The problem arises in the moby/buildkit package, which uses semconv/v1.17.0 instead of v1.21. https://github.com/moby/buildkit/blob/b9fcd7688a5d7d4461f0c1706216b6d4b3e584e6/util/tracing/detect/detect.go#L15
It's not your fault, of course, but I think it's worth telling you about it.
A detailed description of the error and how to reproduce it is here
https://github.com/testcontainers/testcontainers-go/issues/2050
Steps To Reproduce
No response
Compose Version
No response
Docker Environment
No response
Anything else?
No response
Thanks for the report! We've had some OTel dependency conflicts recently across the Docker/Moby projects (the versioning/dependency trees are very complicated and made this quite difficult, unfortunately).
This should be fixed soon, I'll update this issue when it is and work with the testcontainers team to get things updated there as well.
I ran into this issue too.
Error: Received unexpected error:
conflicting Schema URL: https://opentelemetry.io/schemas/1.24.0 and https://opentelemetry.io/schemas/1.21.0
@EwvwGeN did you ever find a workaround?
@zoop-btc as a result, I used two separate containers. Considering that I had an incompatibility error 1.17 and 1.21, and you already have it linked to other versions, they made a bug again