Open Roberto6969 opened 4 years ago
I don't have this problem... But does docker-compose build
before running up
fix it?
Do you mean if I run docker-compose build before docker-compose up -d? Yes, but the message is: "grafana uses an image, skipping"
I had a weird bug with Grafana. It was actually ignoring the env file, but only changes I had made to it after I initially started it up. Try removing the container and image, and starting it again that way. It seems like the container isn't picking up changes to the env file once instantiated.
From my experience:
Hello,
is there any way to diagnose why Grafana ignores every change in grafana.env? When I change parameter in grafana.env and recreate container (docker-compose up -d), I get: nodered is up-to-date portainer is up-to-date influxdb is up-to-date Recreating grafana ... Recreating grafana ... done
OK, it seems recreaction process found out i had made a change to grafana.env. But why Grafana does not take any new parameter (for example new admin password: GF_SECURITY_ADMIN_PASSWORD=whatever)?
Thank You!