Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage volume erased after the containers getting down #464

Closed
rahimbtc opened this issue Nov 23, 2021 · 4 comments
Closed

Storage volume erased after the containers getting down #464

rahimbtc opened this issue Nov 23, 2021 · 4 comments
Labels

Comments

@rahimbtc
Copy link

hello ;
why the storage volume (ex. members and teams) getting deleted after the containers getting down !
how to avoid that ?

@eljeffeg
Copy link
Collaborator

@garanews you know what could be causing this? I'm still learning the particulars of docker.

@garanews
Copy link
Contributor

The db file is created under /opt/rtb of webapp container.
The mapped volume instead is mapping /opt/rtb/files so just a subfolder.
If rebuild image, then db is deleted, but if you just stop and start container, the file is not deleted and data should not being deleted.
I have just tried and can confirm this.

@eljeffeg
Copy link
Collaborator

That makes sense.. when using a sqlite database, we should be creating it under the files directory.

eljeffeg added a commit that referenced this issue Dec 10, 2021
@eljeffeg
Copy link
Collaborator

@rahimbtc I pushed up a fix 8d79106 that should address future docker builds. For existing builds, move the rootthebox.db file into the files directory. Then update the rootthebox.cfg and set the sql_database option to files/rootthebox.db.

@eljeffeg eljeffeg added the bug label Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants