It really depends on what is your use case. For small projects, single machine deployment, it should not be a problem at all, but still take precautions regarding the persistence part.
One question though, even if we consider using the preferred Volumes approach, why would we need to have precautions and what precautions do we need to have? Can you give some idea around it? Are we questioning the implementation of volumes in docker or some other external variables like if the host machine's storage ran out or situations like if someone or some thing deleted our volumes from outside our container?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It really depends on what is your use case. For small projects, single machine deployment, it should not be a problem at all, but still take precautions regarding the persistence part.
One question though, even if we consider using the preferred Volumes approach, why would we need to have precautions and what precautions do we need to have? Can you give some idea around it? Are we questioning the implementation of volumes in docker or some other external variables like if the host machine's storage ran out or situations like if someone or some thing deleted our volumes from outside our container?