-
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
Plugin v3.8.0 does not load: "Could not find Chrome (ver. 116.0.5845.96)" from puppeteer #449
Comments
I have the same issue (saying it is compiled for another architecture) and it keeps restarting Grafana because of this. Reverting to 3.7.x resolves the issue. I'm not running the plugin or Grafana in Docker, but plain on the system (RHEL 7). Running the reported faulty
|
Exactly the same error here. Running it native on AWS EC2 centos 8 stream AMI based. We also tested to manually install the documented yum dependencies according to https://grafana.com/docs/grafana/latest/setup-grafana/image-rendering/troubleshooting/ |
Hello! Thank you for reporting this, we are investigating this issue and we'll keep you updated. |
What happened:
Image renderer plugin version 3.8.0 does not load, giving logs:
And, the usual:
log.txt
How to reproduce it (as minimally and precisely as possible):
Build the official(?) Grafana-with-Image-Renderer Dockerfile, then run the docker image.
Anything else we need to know?:
3.7.2 works.
Directly using the official images
grafana/grafana
orgrafana/grafana:latest-ubuntu
, and passing-e GF_INSTALL_PLUGINS="grafana-image-renderer"
, also does not work. 3.8.0 still does not load; 3.7.2 does load (but would not actually work on those images due to missing dependencies).Setting
GF_PLUGIN_RENDERING_CHROME_BIN
does not fix it.If I use
strace
and try to run 3.8.0 directly, I can see an error on a path that doesn't exist just before the error message is printed. No folders namedpuppeteer
exist in the container. 3.7.2 more correctly tells me not to run a plugin directly.Environment:
20.10.25-0ubuntu1~22.04.2
(which is after the recent chown issue)The text was updated successfully, but these errors were encountered: