-
I've recently migrated a bunch of my docker setups to one central instance of Portainer, with different stacks grouping my containers into purpose. For example, my new Tesla stack runs teslamate, grafana, postgres, and mosquitto. I used to have all that in a docker-compose file, but obviously, that's no longer needed with the new setup. So now, when I run the standard command to create a backup file:
I get an error:
This is obviously because I don't have a docker-compose.yml file any more. I tried changing it to just use docker, with the lower-case T option:
But that also doesn't work. It just exports the dump script itself into the backup file, instead of the actual DB "doing" stuff. What's the right way to create a backup if I'm not using docker-compose? I thought it would be easy, but I'm obviously missing something. Thanks very much! |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
You need to use the container id instead of "postgres". |
Beta Was this translation helpful? Give feedback.
-
I use Portainer as well, but still use docker-compose to easily set-up the initial start of all containers, including naming services and creating networks. |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Hi Guys, I'm using the Hassio addon https://github.com/matt-FFFFFF/hassio-addon-teslamate and I don't know how to export the data to import it into my new Raspberry with the standalone version. Does anyone have any ideas? Portainer runs on the Hassio. |
Beta Was this translation helpful? Give feedback.
You need to use the container id instead of "postgres".