You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Litestream recommends running as a sidecar in Docker, which means exposing the same DB to multiple containers. But is this really supported? I previously researched such a setup, and arrived at the sqlite forum... key quotes:
Question:
I think VM/docker volumes do not work with WAL mode for the same reasons as WAL mode not working on network disks (guess: two OS's do not know about each others locks).
Part of the answer
Docker is like a dory (a wee little row boat) that has a hole in the bottom. It matters not whether you put your dory on the Ocean or a Lake, or even in the toilet. Water will still perculate up through the holes and drown you.
Did I allow myself to get too scared by those quotes? What are the implications for litestream?
I arrived here not as a (current) litestream user but as someone who has a strong interest in running a similar setup. I apologize if opening an issue for this was not the way to go forward, I'm happy to take the discussion to a different location if that's more appropriate.
The text was updated successfully, but these errors were encountered:
Litestream recommends running as a sidecar in Docker, which means exposing the same DB to multiple containers. But is this really supported? I previously researched such a setup, and arrived at the sqlite forum... key quotes:
Question:
Part of the answer
Did I allow myself to get too scared by those quotes? What are the implications for litestream?
I arrived here not as a (current) litestream user but as someone who has a strong interest in running a similar setup. I apologize if opening an issue for this was not the way to go forward, I'm happy to take the discussion to a different location if that's more appropriate.
The text was updated successfully, but these errors were encountered: