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
Storing the tempo-query binary under /tmp in the docker image causes problems when running on a read-only fs #434
Comments
Yeah, the storing the file in Will leave this open b/c I think it should be fixed anyway. |
Sounds great! For anyone with the same problem: |
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. |
Nowadays you need to use env variable
This is useful if you need to enable Kiali to work with Tempo. Related issue here: |
Describe the bug
https://github.com/grafana/tempo/blob/master/cmd/tempo-query/Dockerfile#L6-L9
The tempo-query docker image ships with the binary under /tmp. Some k8s envs are configured with read only file systems so in order to have a writeable /tmp that have to be mounted which in turn removes the binary. To make matters worse the base image
ships without any utils that would make it possible to move the binary using an init container.
Expected behavior
The binary to somewhere other then /tmp :-)
Environment:
The text was updated successfully, but these errors were encountered: