#Hello everyone I have a strange problem

1 messages · Page 1 of 1 (latest)

grave junco
lusty kettle
#

I saw that. As I know it looks like is configured everything fine in NAbox.

#

Weird thing that after submiting data we have issue with grafana.ini

#

we lose configuration

grave junco
#

yes, seems non-ideal. Let's see what Yann says. If I recall correctly, he mounts some of the docker volumes read-only and sounds like maybe the change is happening there and not persisted??

lusty kettle
#

we must have the path to /var/lib/grafana/ldap.toml because if not, LDAP conf in Grafana gets information from an empty ldap.toml file, which also returns to default settings after sending data in NAbox

lusty kettle
#

in docker grafana.ini is read-only

grave junco
#

if I recall, Yann is mounting the host file system into (some?) of the containers, so the distinction between "outside" and "inside" is fuzzy 😃

lusty kettle
#

"outside" - I mean that I can open file outside the docker and save it

#

there is path to docker file

#

"inside" - after open the docker

#

without changing the path to ldap.toml NAbox and Grafana fetches data from 2 different files

grave junco
#

that distinction falls apart when you mount the host file system inside the container or vice-versa. it may have only been the /proc filesystem that was mounted inside, perhaps so containers can see host processes. I only noticed last time I was looking at an nabox system and noticed ps from the host side was returning processes that didn't exist... but I've never tried to setup LDAP. @timber adder should be able to answer. Looking at his documentation, he doesn't mention editing files directly, but I understand why you're doing that

lusty kettle
#

Okay, but it's still weird that the files fall back to their default settings... I have to go now, but I will definitely come back to it. Thank you very much for your time, Chris. Bye for now!