GrafanaDB does not exist after yml upgrade

[adieball]

Describe the bug
After upgrade of docker-compose .yml according to manual here on GitHub Grafana doesn't start anymore and complains "GrafanaDB does not exist"

Error response from daemon: Bind mount failed: '/volume1/docker/TeslaLogger/TeslaLogger/GrafanaDB' does not exists

To Reproduce
Steps to reproduce the behavior:

** Teslalogger Type **
Docker on Synology

Additional context
Add any other context about the problem here.

[Adminius]

Duplicate with #1078

[adieball]

I checked #1078 and went through creating the folder and give it 777.
Still, I get the same message:
Error response from daemon: Bind mount failed: '/volume1/docker/TeslaLogger/TeslaLogger/GrafanaDB' does not exists

@bassmaster187

[adieball]

@bassmaster187 any help here? If possible I'd also pay for some professional help to get it up and running again

[bassmaster187]

Did you really create a GrafanaDB folder and give it 777

Please post the content of your Teslalogger folder (ls -l)

[adieball]

@bassmaster187 Stupid me ... I added the folder in the wrong directory (Teslalogger instead of Teslalogger/Teslalogger)

Grafana container is now starting but there are no dashboards.
Did a docker-compose stop
docker-compose build
and docker-compose up - d
again already without any changes.

[adieball]

I don't see any dashboard in Teslalogger web ui nor in Grafana

a database connection in Grafana does exist and works fine when clicking on test

[bassmaster187]

did you try to restart the whole container? basically it should rebuild all dashboards after every restart. That's how we are able to update dashboards with an Teslalogger update.

[adieball]

yes, I even did a fetch and build

[adieball]

any additional ideas @bassmaster187 ?