feat(docker): upgrade litestream to v0.5.0 #3165
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sanbyk
approved these changes
Oct 8, 2025
|
@DragonStuff @sanbyk Thank you very much for the PR. Of course I will review this PR shortly, but just want to confirm, do you plan to actually use dstack with Litestream? |
peterschmidt85
requested changes
Oct 8, 2025
Co-authored-by: Andrey Cheptsov <[email protected]>
Co-authored-by: Andrey Cheptsov <[email protected]>
|
@peterschmidt85 Incredible, you are so fast at reviewing, I apologize as I was just about to test and I think I inconvenienced you with my typo. Thank you very much for fixing my PR up! Looks like it builds successfully, and I'm going to run this image on our infra as well to test. Details
|
|
|
@peterschmidt85 Good catch. After working with Litestream on another project, it has a few caveats and is definitely still pre-v1. Perhaps going down the route of using PostgreSQL is a good option, but I was thinking it would be really nice to not have another PostgreSQL database to manage. Don't worry, I totally understand the risks of basically having a single server for I've written a short bash script to implement the 
After deleting the container and restarting, it comes up correctly as well. 
Perhaps in a follow-up PR it would be good to add additional arguments to allow Litestream args to be set from environment variables. |
peterschmidt85
approved these changes
Oct 8, 2025
There was a problem hiding this comment.
From my side, it looks good. @r4victor please have a look too just in case!
|
@DragonStuff Merged. Please give it a thorough test, and let us know if all is good! |
@peterschmidt85, we did some testing overnight with a service running, with the dstack deployment on spot instances to make sure it gets interrupted a few times and everything seems to work as expected. We will keep this running for our staging environment and if we encounter any issues, I’ll make sure to make an issue and PR to fix it. Thanks again for your prompt assistance, dstack is awesome! 🥂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The SRE team at TableCheck is attempting to deploy dstack for our GPU workloads, but we are currently blocked due to an issue we have identified with EKS Pod Identity (OIDC) support and Litestream.
This pull request in Litestream adds support benbjohnson/litestream#683, but the version of litestream used in dstack's Docker images is quite old (v0.3.9) and doesn't include this support.
As a result, the Docker image will start with the following error from Litestream:
This pull request updates the version of Litestream to the latest version available in https://github.com/benbjohnson/litestream/releases.