19
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
19 points (100.0% liked)
Selfhosted
60934 readers
884 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. Tags [CBH] or [AIP] are required, see the links in Rule 8 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, and find example disclosures here.
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 a directory in my home folder for all my different docker containers. I back that up like my other critical files on my NAS, Backup NAS, cloud storage and external drive. Its all scripted to happen periodically.
The docker compose files I also upload to my local Git so I can version them. Make the git ignore skip everything that isn't a .yml
If you would want to spin them up again, yeah you could just copy them in a new place, make sure the docker-compose.yml is at the top and docker-compose pull the image, then docker-compose up. If your yml specifies that your configs are ./ , it'll know to look for them in the same folder as your yml and begin its file paths there. Anything outside your ./ in theory should be read only or be some kind of data off a NAS that is independent from the service. Its just not best practice in my eyes for your docker application to write outside of the folders beneath its docker-compose.yml location.
Just organize your volumes correctly and you can move the docker container anywhere you want with a copy paste and a docker-compose up. Imo docker-compose is WAY easier and faster than any GUI instance of Docker.
So I have filesystem backups of the entire thing (using proxmox backup server) and a replicated image of the docker-volume and all subvolumes that's both snapped locally and replicated to a NAS at my condo about 200 miles away.
I think I'm covered. I even tried brinigng up the server on the Truenas there and it worked like a champ...All I ahve to do is fail my cloudflared over and everything would automatically come up on the remote location without me even having to muck about with DNS.
I don't mess with Git...I should...but that's a new set of lessons. :)