Skip to content
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

Example Docker Project Errors : basic_phoenix_ecto #343

Open
albsch opened this issue Jun 23, 2024 · 0 comments
Open

Example Docker Project Errors : basic_phoenix_ecto #343

albsch opened this issue Jun 23, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@albsch
Copy link

albsch commented Jun 23, 2024

Describe the bug

  • Dependency resolution fails when doing step 2. of the example.
> mix deps.get, ecto.setup                                                                                                                            
Resolving Hex dependencies...                                                                                                                            
Resolution completed in 0.277s                                                                                                                           
Because the lock depends on opentelemetry 1.2.0 which depends on opentelemetry_api ~> 1.2.0, the lock requires opentelemetry_api ~> 1.2.0.               
And because every version of opentelemetry_cowboy depends on opentelemetry_api ~> 1.3, the lock is incompatible with opentelemetry_cowboy.               
And because your app depends on the lock, no version of opentelemetry_cowboy is allowed.                                                                 
So, because your app depends on opentelemetry_cowboy, version solving failed.                                                                            
** (Mix) Hex dependency resolution failed
otel-1      | * error decoding 'exporters': unknown type: "jaeger" for id: "jaeger" (valid values: [skywalking debug dataset mezmo azuremonitor clickhouse logicmonitor pulsar sentry awscloudwatchlogs awsemf awsxray influxdb kafka loki tencentcloud_logservice elasticsearch file honeycombmarker loadbalancing open
search prometheusremotewrite coralogix googlecloud instana datadog logzio otelarrow splunk_hec zipkin otlphttp alibabacloud_logservice cassandra googlecloudpubsub googlemanagedprometheus opencensus prometheus sapm alertmanager awss3 azuredataexplorer carbon signalfx syslog sumologic nop otlp awskinesis])       

Expected behavior
Dependencies get resolved and otel container starts.

Additional context

Environment:

Erlang/OTP 27 [erts-15.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit:ns]
Elixir 1.17.1 (compiled with Erlang/OTP 27)

Deleting the lock file and re-fetching the dependencies seems to work. I have not investigated further why dependency resolution fails.

@albsch albsch added the bug Something isn't working label Jun 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant