Definitely a consideration. In my case, the vast majority of my services are running in docker on a single host box, including the reverse proxy itself (Traefik). That unencrypted traffic never goes out over a wire, so for now I’m not concerned.

I’m not super paranoid about security, but I do try to have a few good practices to make sure that it takes more than a bot scanning for /admin.php to find a way in.

• Anything with SSH access uses key-based auth with password auth disabled. First thing I do when spinning up a new machine
• Almost nothing is exposed directly to the Internet. I have wireguard set up on all my devices for remote access and also for extra security on public networks
• Anyone who comes to visit gets put on the “guest” network, which is a separate subnet that can’t see or talk to anything on the main network
• For any service that supports creating multiple logins, I make sure I have a separate admin user with elevated permissions, and then create a non-privileged user that I sign in on other devices with
• Every web-based service is only accessible with a FQDN which auto-redirects to HTTPS and has an actual certificate signed by a trusted CA. This is probably the most “paranoid” thing I do, because of the aforementioned not being accessible on the Internet, but it makes me happy to see the little lock symbol on my browser without having to fiddle around with trusting a self-signed cert.

One of the things I like about containers is how central the IaC methodology is. There are certainly tools to codify VMs, but with Docker, right out of the gate, you’ll be defining your containers through a Dockerfile, or docker-compose.yml, or whatever other orchestration platform. With a VM, I’m always tempted to just make on the fly config changes directly on the box, since it’s so heavy to rebuild them, but with containers, I’m more driven to properly update the container definition and then rebuild the container. Because of that, you have an inherent backup that you can easily push to a remote git server or something similar. Maybe that’s not as much of a benefit if you have a good system already, but containers make it easier imo.

I’ve always been hesitant to host any services on a device with a non-removable battery. Having a battery constantly charging and discharging isn’t great for it and could potentially be a fire hazard. I know modern devices have gotten much smarter about how they charge, so maybe it’s not as much of an issue anymore, but still something to be aware of depending on how old your phone is or how you modify the firmware.

Personally, with how cheap you can find a mini PC or SBC, I would just save up a bit (maybe even sell the device you’re planning to host on) and keep an eye out for deals. You’re going to get a lot more freedom and power with those devices, and not have to try to hack around the limitations of a mobile OS.

My advice for security is don’t expose anything to the Internet unless you’re sure you know how to secure it. If you want to be able to access self-hosted services remotely, setting up a VPN is the way to go. OpenVPN is gonna be the most widely supported way of doing that. In fact, based on a quick Google search, it looks like your router has an OpenVPN server built in. If you’re willing to put in some effort for something more modern and performant, look into WireGuard.

Another benefit of having a VPN is that if you set it up to allow access back out to the Internet, you can use it to mask your internet traffic while you’re connected to an untrusted network.

That sounds interesting. Thanks for the recommendation!

Part of me is starting to wonder, honestly. I will say that the web UI for TrueNAS Scale is leagues better than Unraid’s, which to me always felt confusing and hacked together. ZFS is also really nice, although Unraid did recently add support.

One pain point I’ve run into with TNS is that access to Docker or Kubernetes seems to be intentionally locked down from access anywhere but the built in apps catalog. As someone who works with Docker and various orchestration engines professionally, I much prefer being able to define and stand up my own services to using a list of predefined templates. There are obviously ways of getting around the restrictions in TNS, but with Unraid, I could install something like Portainer or simply drop into the terminal and run docker commands myself. Not having that is frustrating.

Overall though, I think TrueNAS is a much cleaner and more modern user experience, so long as you stay on their rails. Which I suppose is the point.

I looked at doing two vdevs but was put off by the lower usable storage. At a certain point, maybe that’s not as important as I think though.

Yeah, the choice for 6TB wasn’t my best. I got the two older drives a few years back on a Newegg flash sale, and it seemed like plenty, especially considering Unraid’s model of 1 parity drive and 100% usable storage on the data drive(s). Then, when I decided to upgrade, I was too cheap to go buy 4 whole new drives, so I just went with more of what I already had (to add insult to injury, they’re all WD Red drives…).