when run in containers ,what are the best practice...
# troubleshooting
h
when run in containers ,what are the best practices for managing state?
a
The container has a volume mount to the local file system in the default recommended way to run. In that case state is implicitly handled by sqlite db in .meltano dir. If you are not using a volume mount and truly running it ephemerally, it gets more complicated.
h
I saw there is an issue in Product Roadmap to introduce a remote state backend. https://github.com/meltano/meltano/discussions/6270 Q1: Does it mean with the new state backend feature, there will be no more need to use a volume mount as persistent storage? Q2: Besides states, does meltano store other “states” that must be persisted outside of containers?
e
There’s no need to mount a volume in the present state AFAICT. You can point the system db to an external postgres db.
a
@huiming - @edgar_ramirez_mondragon is correct. 👆 Re:
Q1: Does it mean with the new state backend feature, there will be no more need to use a volume mount as persistent storage?
More precisely, that issue would allow you to run without a volume mount and also without an RDBMS.