-
Notifications
You must be signed in to change notification settings - Fork 51
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
Hardcoded jaeger path #11
Comments
The path is configurable like the readme says https://github.com/pavolloffay/jaeger-clickhouse#run |
We should change the run command to run Jaeger all-in-one from docker and inject the compiled plugin via volume. |
Something like this could work, but it doesn't. I didn't dig into it.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Make considers path to jaeger all-in-one as
${HOME}/projects/jaegertracing/jaeger/cmd/all-in-one/all-in-one-linux-amd64
, maybe it's better to make environmental variable for thisThe text was updated successfully, but these errors were encountered: