15
Docker, Truenas, and self-hosting...
(shredderfood.net)
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 08 Jul 2026
15 points (100.0% liked)
Selfhosted
60542 readers
579 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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.
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 3 years ago
MODERATORS
I have another container running the proxmox backup client that does a filesystem dump daily... Not bad, but I think postgres may not recover from that...
Right now 2 weeks of daily replicated snapshots are probably as good as I'm going to get...
Works fine... Most of the time. As long as the file gets saved at an instant in time (e.g. zfs snapshot), postgres sees it like a power failure and restores. You want to have several recent backups if you do this because it will occasionally fail.
Saw an article that says proxmox backup client can be set up to be ZFS aware...will have to do more reading... (for backups)
Replication is always a point in time, and I keep two weeks worth of dailies.
Test it, find out.
Well that worked... Amaze! I copied the lemmy directory to my user directory, made the necessary changes in docker-compose, and boom, it came up. If I were to script the changes using sed, I could even have a full DR failover.
Not a bad idea...I'll have to make some network changes in the docker compose and build a new macvlan for it...but it should be easily addressable by IP address. I did to a test startup of my mastodon DB and that did seem to work...
And I should probably block outbound traffic just to be sure it's not trying to update the fediverse...
Cool, now I know what I'm playing with tonight. :)