Unable to restore a teslamate database backup using docker compose (v2) about teslamate HOT 8 CLOSED

The error no configuration file provided: not found usually comes, when you do not run the docker compose command in the directory, where the docker-compose.yml is located.

from teslamate.

The error no configuration file provided: not found usually comes, when you do not run the docker compose command in the directory, where the docker-compose.yml is located.

Thanks for that info @DrMichael.

Since I am using Portainer with Stacks, Portainer seems to create the docker-compose.yml & .env files under /var/lib/docker/volumes/portainer_data/_data/compose/X/vY where X is a folder for each separate Stack and vY is the incremental version for that Stack, as each change/configuration is re-deployed.

In my case the current path to the latest Stack version containing the most up-to-date docker-compose.yml & .env files is: /var/lib/docker/volumes/portainer_data/_data/compose/53/v16 (yes, I made a lot of tuning and re-deployments LOL)

After the teslamate.bck backup file was copied to that folder, I accessed the folder as root and attempted to issue multiple import commands (using all possible names for the postgres database) with no success:

root@server:/var/lib/docker/volumes/portainer_data/_data/compose/53/v16# sudo docker compose exec -T database psql -U teslamate -d teslamate < teslamate.bck
service "database" is not running <<< ERROR

root@server:/var/lib/docker/volumes/portainer_data/_data/compose/53/v16# sudo docker compose exec -T postgres psql -U teslamate -d teslamate < teslamate.bck
service "postgres" is not running <<< ERROR

root@server:/var/lib/docker/volumes/portainer_data/_data/compose/53/v16# sudo docker compose exec -T teslamate-postgres psql -U teslamate -d teslamate < teslamate.bck
service "teslamate-postgres" is not running <<< ERROR

Any other suggestions?

from teslamate.

What gives docker compose ps?

from teslamate.

No support for portainer

from teslamate.

What gives docker compose ps?

@JakobLichterfeld why did you close this ticket? Does it say anywhere in the teslamate documentation that managing Docker with Portainer is not supported, or is this your decision? Also all commands are done via SSH and directly using Docker and Docker Compose, just like the manual says.

@DrMichael, here is the formatted output of Docker ps (using docker ps --format "table {{.ID}}\t{{.Names}}\t{{.Image}}\t{{.Ports}}" for legibility). I blurred out other unrelated containers...

I even tried using the container ID instead of "database" and same result:

sudo docker compose exec -T aa9613a55758 psql -U teslamate -d teslamate < teslamate.bck
service "aa9613a55758" is not running

Hoping you have another suggestion...

from teslamate.

https://docs.teslamate.org/docs/installation/docker/ --> remove the unneeded complexity of portainer or know what you are doing

from teslamate.

@JakobLichterfeld it indeed is not a portainer but rather a docker compose issue...

@SemoTech You're missing the service in the ps reault. You need to use the service in the docker compose.

from teslamate.

new issue #3976

from teslamate.