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

A tip about docker upgrades and static volumes #37

Open
IVTore opened this issue Feb 14, 2024 · 1 comment
Open

A tip about docker upgrades and static volumes #37

IVTore opened this issue Feb 14, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@IVTore
Copy link

IVTore commented Feb 14, 2024

A tip about docker upgrades and static volumes.
Hi,
I observed that your docker compose file generates static volumes intrinsic to docker file system.
This may seem to be advantageus for "it runs on my computer" problems.
But in my experience it may cause trouble during upgrades (not your code upgrade).
In rare cases of docker upgrades, docker may mess up the internal docker file system.
I lived through three such events.
I would advise you to carry these volumes to host file system, at best to the directory of installation like ./database etc.
Thanks for your interest.

@IVTore IVTore changed the title Hi, A tip about docker upgrades and static volumes Feb 14, 2024
@jameszyao jameszyao self-assigned this Feb 14, 2024
@jameszyao
Copy link
Contributor

@IVTore Thank you for constructive feedback. We'll take it into consideration and improve the deploy process.

@jameszyao jameszyao added the enhancement New feature or request label Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants