bassmaster187 / TeslaLogger

TeslaLogger is a self hosted data logger for your Tesla Model S/3/X/Y. Actually it supports RaspberryPi 3B, 3B+, 4B, Docker and Synology NAS.
https://www.teslalogger.de
GNU General Public License v3.0
517 stars 171 forks source link

Synology upgrade unable to locate GrafinaDB #1078

Open IMgoRt opened 1 year ago

IMgoRt commented 1 year ago

Following the usual update instructions, on the last step docker-compose up - d the following occurs

ERROR: for grafana Cannot start service grafana: Bind mount failed: '/volume1/docker/TeslaLogger/TeslaLogger/GrafanaDB' does not exists

Attempting chmod 777 TeslaLogger/GrafanaDB gives: chmod: cannot access 'TeslaLogger/GrafanaDB': No such file or directory

bassmaster187 commented 1 year ago

The Problem is, you have to create it by yourself. An empty folder should do it. But why, I don't know. It should be automatically created as described in docker docs. https://docs.docker.com/storage/bind-mounts/#differences-between--v-and---mount-behavior

I'll try to check if there is another solution.

IMgoRt commented 1 year ago

The Problem is, you have to create it by yourself. An empty folder should do it. But why, I don't know. It should be automatically created as described in docker docs. https://docs.docker.com/storage/bind-mounts/#differences-between--v-and---mount-behavior

I'll try to check if there is another solution.

Thanks, that fixed it, but it leads to this issue: https://github.com/bassmaster187/TeslaLogger/issues/1076

hagmann-sg commented 1 year ago

creating a empty folder works for me too 👍 the GrafanaDB error disappear but now i have the issue with the #1076 and i think all my data are gone :-(

adieball commented 1 year ago

Weird, doesn't work for me at all

Created the folder and did a chmod 777, still the same issue