Nobody thinks about Docker backups when everything is working. The dashboard loads. The media server streams. The reverse proxy behaves. The database container has a cute little green “healthy” status. Life is good. Then one day you run an update, delete the wrong volume, lose a disk, break a Compose file, or discover that the “temporary” container from six months ago was actually storing something important. That is when Docker stops feeling magical and starts feeling like archaeology. This post is a practical guide to backing up Docker containers on a Linux home server . Not enterprise disaster recovery. Not Kubernetes. Not a 40-page policy document. Just a realistic backup plan for a homelab running Docker Compose, bind mounts, named volumes and a few services that became more important than expected. The main idea is simple: You do not really back up containers. You back up the things needed to recreate them, plus the data they would destroy your weekend by losing. ...
SSH is usually the front door of a Linux home server. And if that door is reachable from the network, something will eventually knock on it. Sometimes it is you. Sometimes it is a script from the other side of the planet trying admin , root , test , ubuntu , oracle , minecraft , and whatever else is in its boring little dictionary. This is where Fail2ban is useful. Fail2ban watches logs for repeated failed login attempts and temporarily bans the source IP address using firewall rules. It is not magic, and it is not a replacement for proper SSH hardening, but it is a very useful extra layer for a Linux home server. This post is a beginner-friendly guide to Fail2ban for SSH on a Linux home server . The goal is not to build an enterprise security platform. The goal is to reduce brute-force noise, protect SSH, and avoid locking yourself out of your own machine. If you are building a secure Linux box, also see my Linux Home Server Security Checklist and my guide to UFW Firew...