90
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Mar 2026
90 points (96.9% liked)
Selfhosted
57705 readers
349 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Hi,
The agent need to be on the same network as your database. You can either include the agent in the same Docker Compose setup or create a Docker network to link them. I’m not sure what you mean by 'persist across restarts.' Can you clarify? However, it works perfectly fine with databases running in Docker.
For Redis and Valkey, hot restores are unfortunately not supported. You need to stop the services and perform some manual operations. This limitation is why backups are mainly useful for disaster recovery rather than live rollback.
Feel free to ask any other questions or clarification if needed.
Thanks for the clarification. By "persist across restarts," I'm referring to the fact that if I just install the agent in my container, it won't persist if I restart the container, unless I install it on a volume which seems clunky. Running the agent alongside in a separate container with network access is the solution I was looking for.
On the Redis and Valkey restores, that makes sense. Disaster recovery is my use case anyway. Do you document the manual restore process for those? I didn't notice it in a brief review of the docs, but I may have overlooked it.
No, we haven’t documented it yet, but that’s a good idea. I’ll add it to the backlog, and we’ll work on it soon!