Closed petertjmills closed 12 months ago
The permissions wasn't the problem. It was my misunderstanding on grafana. I misunderstood what the docker-compose file was binding. I, completely and wrongfully, assumed /etc/grafana/provisioning
was how it persisted data, but it's not, it's how it provisions files. In retrospect I should have seen this.
For persistent storage:
volumes:
# we assume cwd == /var/lib/faasd
- type: bind
source: ./grafana/
target: /var/lib/grafana/
Apologies for opening an unnecessary issue. This may make a good addition to the book, for reference.
Hi @petertjmills no worries.
What did you change vs. the eBook / DevOps Pro tier files?
Alex
Due diligence
My actions before raising this issue
I don't know if this is a faasd, grafana, containerd, or basic linux file permissions issue, I've been following the Serverless for everyone else book, but am having an extremely hard time trying to get grafana to use the volume, provided in the
docker-compose.yaml
file. I have the devops pro edition, and noticed thegrafana.yaml
and the config are different in that in the book it is implied to use 1000 as a user, and in the yaml there is an account named 'grafana'. I've tried to use both creating both a faasd user 1000, and a grafana user with uid 472. I'vechown
'd andchmod
'd the folder in all number of different configurations, and I'vechmod
'd everything to 777. Grafana shows the same errors in the logs.Why do you need this?
To use grafana with persistant storage, with faasd.
Who is this for?
Proof of concept for a commercial functions platform.
Expected Behaviour
Grafana creates the required directories in the mounted folder.
Current Behaviour
No files being created, grafana forgets all dashboards on restart.
List All Possible Solutions and Workarounds
Which Solution Do You Recommend?
Steps to Reproduce (for bugs)
Your Environment