-
Notifications
You must be signed in to change notification settings - Fork 152
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
Image renderer plugin 3.4.2 appears to be incompatible with Grafana 9.0.3 Alpine Docker image #358
Comments
Unfortunately not fixed with plugin 3.5.0 |
And still an issue with Grafana 9.0.4 |
Same issue with grafana version grafana/grafana@7742190 and renderer 3.5 |
Same issue grafana:latest (9.05), renderer 3.5. |
With grafana 9.0.6 and renderer 3.5.0 I have the same issue. |
With grafana 9.0.7 and renderer 3.5.0 I don't have this issue anymore. |
Maybe is related to this?: #320 (comment)
|
I don't think so. |
when I install plugin image renderer => I can't start container grafana. did something go wrong? |
When you start Grafana what is the error in the logs? @vqmanh |
when I removed grafana-image-renderer, I could start grafana container |
Anyone know of a way to diagnose this further? "Unrecognized remote plugin message: \n\n" is pretty unhelpful. |
I also face the problem, anyone can help me? |
i have find some reasons about this problem; first, you should set the log level to debug, and you will find the detail error in start log; for example, my problem is about the Glibc or libC++ version is too low. second, according to the debug error, may be you can find some solutions.
|
Still an issue with grafana 9.3.2 and plugin 3.6.3 when running Grafana as Docker image and installing plugin using CLI
Edit: actually found that in the readme it already says for Docker setup to run this as separate container. So guess my case is different. |
@akamensky did you manage to resolve this problem? I have the same versions of grafana and image renderer and I'm facing the same issue. |
@Davenury Actually yes. For Docker setup we run this plugin in another container and configured Grafana to connect to it. That's in the readme of this project (I should've updated my comment). |
@akamensky could you provide more details 😅 I've been also trying to make it work from the grafana helm chart but I receive mutliple errors from renderer (also renderer eats 10GB of RAM, so I suspected a memory leak)? |
I just read documentation as described in readme file. I suggest you check that too perhaps? We are using Docker so no idea about running it in k8s or other systems using helm charts. I think documentation or devs of this project are better placed to help you.
I am not a dev of this project so I can't say for memory leaks. But it is literally Chrome browser, so 10GB is quite normal for that IMO |
Tested with latest versions (Grafana 9.4.7 and image renderer 3.6.4) and it's working now. @Davenury You can find a simple docker-compose example here and more complex examples in the parent folder. If you still have trouble running the image renderer as a separate container, please open a new issue with your current configuration. |
faced this issue with grafana 9.5.3 with all the latest versions of plugins. ether remove that line or force link glibc again with
this should solve the issue |
What happened:
Grafana 9.0.3 in Alpine Docker image fails to start when Grafana Image Renderer is enabled. The latest version of the plugin right now is 3.4.2.
9.0.2 works. Ubuntu Docker image works. Alpine image is 3.15.4 in case of both 9.0.2 and 9.0.3.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Logs:
The
ld-linux-x86-64.so.2
and thesymbol not found
errors also appear in 9.0.2 and the plugin works, so I guess those are red herrings and we need a new plugin release?Environment:
The text was updated successfully, but these errors were encountered: