Replies: 1 comment
-
That directory will store the compose and any bind mounts (assuming you've done ./folder:folder). If you're using environments within the GUI it only temporarily creates the .env file and removes it after the container has started. Any volumes will be under the usual /var/lib/docker/volumes directory. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
currently i run my own Compose Stacks via docker commandline, all in seperate directories.
I put my compose.yml, env file, additional files and even my persistent data in this directory.
For every container in the stack, that wants to persist data in a volume, I create a subdirectory in this stack directory.
This way I can down the whole stack, wrap it all up in a tar archive and immediately have a consistent backup.
If I understand the workings of Komodo correctly, it also puts most of that stuff (or all? please correct me) in a certain subdirectory, e.g. "/etc/komodo/stacks/demo-immich".
So, can i put everything in there and do my backups the same way?
Is/Will there be a function in Komodo itself to do backups of stacks this way?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions