Open jasonacox opened 11 months ago
Why not use Alpine-based images?
docker.io/grafana/grafana 9.4.14 f69ac1c180a5 7 weeks ago 332 MB
docker.io/grafana/grafana 9.4.14-ubuntu 76a0cce050ec 2 months ago 428 MB
docker.io/library/telegraf 1.28.2-alpine 3d231738b7db 2 weeks ago 210 MB
docker.io/library/telegraf 1.28.2 f10f8ba7295f 3 weeks ago 453 MB
Good question. Is there a reason? Key is to make sure we target all architectures (amd64, arm32, arm64) to ensure it they have builds that run on things from Raspberry Pis, x86 to Macs.
Good question. Is there a reason?
I know I ran into an issue when I was doing my ToU service - alpine does not include gcc (required by pandas). Not sure if this could affect any of the core modules in the dashboard. I also have a memory that there is an issue with RPi support for some of the python versions.
I have switched to alpine-based image for both grafana and telegraf and no issue so far. I'm using podman on arm64 (rpi4)
Looking at their page on dockerhub I can see a difference for telegraf, for which the alpine-base image is not available for arm32. For grafana on the other end I can find the same arch for both ubuntu and alpine version, but it look like that in the last month they have dropped the support to arm32 for both.
This is a proposal to upgrade the pinning to newer version of Grafana and Telegraf:
During testing, the "look" difference between Grafana v9.1.2 and v9.4.14 are minor. There is a subtle adjustment to the font and labeling (IMHO looks better). No issues with panels. The Power Flow Animation required an update to pyPowerwall to accommodate the grafana-dark background color (transparent settings were in use before, but no longer work).
Related discussions: