# Docker Setup
## Synology NAS
Synology users must place the docker inside a special folder:
```
sudo -i
cd /volume1/docker
mkdir teslalogger
cd teslalogger
```

## Docker on Raspberry:
It won't work if you don't have a 64bit OS as MariaDB requires a 64bit OS!

## Install:
Please make sure you have the latest docker and docker compose. Many repositories comes with old docker and / or docker compose. You can avoid a lot of problems by doblecheck it.

```
mkdir backup
mkdir mysql
mkdir invoices
chmod 777 backup
chmod 777 mysql
chmod 777 invoices
wget https://raw.githubusercontent.com/bassmaster187/TeslaLogger/refs/heads/NET8/.env -O .env
wget https://raw.githubusercontent.com/bassmaster187/TeslaLogger/refs/heads/NET8/docker-compose.yml -O docker-compose.yml
docker compose pull
```
You can adjust some settings in your .env file like Timezone (default is MEZ / Berlin)
```
docker compose up -d
```

after a minute or two, everything should be ready. **On some slow machines or NAS, that could take more than 10 Minutes. I even heard about 30 Minutes.** Especially the database may take longer, so don't give up, if Teslalogger can't connect to the DB at the first startup. 

You have to wait untill you can read this in your mariadb container logs:
```
/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/sqlschema.sql
```


Try to connect to Grafana with you favorite browser:
http://localhost:3000 (admin/teslalogger)

Try to connect to Admin-Panel
http://localhost:8888/admin/

Go to Settings / MyTesla Credentials / Edit 1st car
Enter Tesla credentials / Token to connect to your car.

# Docker update / upgrade
Usually, you update the Teslalogger in admin-panel by clicking on update button.
If there are updates of the subsystem, you have to get the latest docker-compose.yam file.

```
docker compose stop
wget https://raw.githubusercontent.com/bassmaster187/TeslaLogger/refs/heads/NET8/.env -O .env
wget https://raw.githubusercontent.com/bassmaster187/TeslaLogger/refs/heads/NET8/docker-compose.yml -O docker-compose.yml
docker compose up -d
```

# Trouble shooting
1. Init scripts like DB table setup not working

On slower devices like NAS devices, the init scripts of Teslalogger might not run successful during the first run. What you can do is restart the teslalogger_teslalogger_1 container after ~ 5 minutes. This should fix missing tables in the database and can easily be obsorved via the log files. Repeat a couple of times if required. A helpful command is:
```
docker restart teslalogger
```

2. Messed up container images or build caches

If you are not running anything else in containers and are stuck with strange behaviour or errors, try cleaning up your existing container images, networks and build caches:
```
docker system prune # make sure all running containers are stopped before
```