Can't start grafana container anymore permission issue

  • What Grafana version and what operating system are you using?

latest grafana/grafana docker container

  • What are you trying to achieve?

Trying to start grafana

  • How are you trying to achieve it?

Starting the container

  • What happened?

Grafana is not starting aymore.

  • What did you expect to happen?
    Grafana to start

  • Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were.

logger=sqlstore t=2023-03-31T16:27:22.590882757+02:00 level=info msg=“Connecting to DB” dbtype=sqlite3
logger=migrator t=2023-03-31T16:27:22.591212875+02:00 level=error msg=“alert migration failure: could not get migration log” error=“failed to check table existence: unable to open database file: permission denied”

  • Did you follow any online instructions? If so, what is the URL?

Yes, so, I wanted to have an idea of who would be visiting a public dashboard I created.
So I followed the instructions here : View Nginx Proxy Manager Access Logs In A Beautiful Dashboard (with goaccess) - Docker Containers - Unraid
I created an extra line in my nginx server in order to log all its logs to a specific log file. And was still able to access my grafana server.
problem is that grafana suddenly became unstable, and all my dashboards values were displaying, then hiding, and displaying again. looking like a christmas tree.

I restarted grafana, and without making ANY change to my grafana docker container, I was now unable to restart it. Log states I have no permission to access the grafana DB !

I’m OK to reinstall grafana, as soon as I’m able to restore my dashboard that took me days to be created.

Please help me, I’m scared al my dashboards are now gone :frowning:
thanks !!!

OK, I fixed this, if anyone wants to know how :

I backed-up my whole grafana docker folder.

cp -r grafana/ grafana_backup/

I reinstalled the docker container from scratch

in the new container folder → rm -rf *

cp -r grafana_backup/* .

chown -R nobody:users *

chmod 777 *

restarted the docker container → back in the game.