Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

Consider a docker volume for app database #1663

Open
jraviotta opened this issue Jul 13, 2018 · 0 comments
Open

Consider a docker volume for app database #1663

jraviotta opened this issue Jul 13, 2018 · 0 comments

Comments

@jraviotta
Copy link
Contributor

I'm interested in comments from the development community about the following user story and architecture feature. Admins, if you prefer to have this discussion on Reddit, I can move it there.

Given I am running zenbot in a docker container, I want my database content to persist after rebuilding containers so that I don't loose my trading history and have to re-import OHLCV data.

Additionally, I want to upgrade zenbot, without losing everything.

Presently, it appears that the app database is stored within the container and is discarded every time the container is re-built. Docker suggests storing data in a named volume so that containers can be created and discarded as needed without losing continuity.

A question about security has been raised as data in a container does persist beyond the life of the container. Additionally, there is a concern that even when the volume is destroyed, user data may still be retrievable from the Docker cache.

If anyone has expertise with Docker, please chime in.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants