True nas is nas software that moonlights as a server. Debian is a linux distro commonly used as the operating system for servers due to its incredible stability and reliability among other things. So reliable infact that it’s used as the operating system for true nas scale! So unless your using the core version (that runs bsd) then your already using it.
As far as rawdogging Debian on your hardware goes, id recommend against it unless you’re looking to seriously up your admin game. No web interfaces, lots of time in the terminal ( command line ) and more configuration files than is anyway reasonable. And we haven’t even started on virtual machines like proxmox ( also Debian based! ) or container critters like docker and kubernetes. (Iirc true nas uses kubernetes under the hood)
___alt-text: The “I lied, I don’t have netflix” meme template. The girl with heavy dark rings around her eyes points a gun at the observer, with various images inserted in the background. The images include references to debian, libreboot, rsync, sed&awk, cron. The text reads: “I lied, I don’t have netflix - Take off your shoes, we’re going to learn to setup a NAS with Debian customized and automated to the bone and also automate the deployment process with Kubernetes. Everything will have 3-2-1 backups and controls will be networked to the volume slider in the radio of your car. We will use the motherboard of your calculator because it’s supported by libreboot.”
Small correction: since the newest version there only is Trunas Scale, so the Debian derivative, which they now call Community Edition. The BSD variant has been decommissioned as far as I know.
What route do I go if I want to up my admin slowly so I eventually feel able to run pure Debian? Currently running Docker on Unraid with two minor VMs but looking to migrate away from Unraid with the intention to only run FOSS (and get a deeper understanding of everything under the hood).
I know that’s little information, all I need is a nudge in the right direction so I can figure things out by consulting documentation and forums.
Realistically, comfort comes from experience. The more you use it the more you’ll feel comfortable.
If you want to get a lot of exposure without dedicating too much time to it and limit the risk, I would say, spin up a Debian VM and try to configure it into the server you want the old school way. Setup ssh keys, raid pool and samba share all via ssh. Try to do it like you’re actually deploying it. This will give you real world exposure to the command line and the commands you’d run. Next maintain that server like it’s production, ssh in every couple of weeks to run updates and reboot. Just that muscle memory of logging in and reviewing updates will help you feel more comfortable. Do it again with another service (a VPN server would be an easy choice, a Minecraft server is also a fun one but requires a lot more memory. DNS would be good if you’re feeling brave, but that’s really just because DNS architecture is more complex than most realize) and maintain those servers too
Once you’ve setup a couple of servers and spent a couple of months monitoring and updating them your comfort level should be much higher and you might feel ready to setup some actually home production servers on Debian or the like.
You mentioned running Trunas and wanting to learn Debian and other FLOSS software, the easy button answer is to run Proxmox. Its free and open source with paid enterprise support plans available and has been rapidly improving just in the handful of years I’ve been running it. Proxmox is really just a modified version of Debian. They have some tweaks and custom kernels over stock Debian but impressively actually have a supported install method of installing overtop of an existing Debian install and apparently some Proxmox employees actually run it as their workstation operating system
I’ve actually been working my way through the proxmox-on-top-of-debian guide recently, but after installing the proxmox-ve kernel and rebooting, I was left with SSH disabled (connection refused) and no local console (more precisely no monitor output past “loading initial ramdisk”). I have so little time on my hands that troubleshooting is sometimes taking the fun out of it. Probably just going to re-install using the Proxmox ISO.
If you can afford it it’s a good idea to buy a Raspberry Pi since Raspbian is basically just debian. Then replicate your current setup on it and just try to tinker with it without any risks of breaking things or losing data.
If you’re using a lot of Docker I would recommend learning the command line since you’ll be able to use Docker on basically any real OS at that point.
Honestly figuring out docker is 50% of the journey with the other 50% mostly being networking. For instance if your looking to start your own Jack Sparrow themed streaming service you’d want to grab a domain name, point it at your ip, open up ports 80 and 443 on your router, install a reverse proxy via docker and set up SSL ( hint: Caddy makes this easy ) and point it at your jellyfin docker container and voila, your very own streaming service you can access from anywhere! Notice the complicated part of all this is mostly the networking and docker setups, not so much the OS that your running. ( Note: don’t open ports without knowing the risks )
Debian is a fine OS but most homelab stuff can be done on anything you can install docker on, even on a windows computer! That’s not to say you shouldn’t learn some Linux server stuff but it isn’t wholly necessary. That being said…
My best advice for getting into Linux servers would be to grab an old PC, laptop or even a raspberry pi and install Debian, raspbian or any other distro on it. Figure out how to log in via ssh and get the thing running headless ( no keyboard or monitor ) and just learning to navigate and do things via the terminal. Some of the basics would be learning to use the package manager to install software, mounting the file system remotely and figuring out how to setup static IPs and such. When your ready go ahead and install docker, follow some tutorials, learn some yaml and your off to the races!
True nas is nas software that moonlights as a server. Debian is a linux distro commonly used as the operating system for servers due to its incredible stability and reliability among other things. So reliable infact that it’s used as the operating system for true nas scale! So unless your using the core version (that runs bsd) then your already using it. As far as rawdogging Debian on your hardware goes, id recommend against it unless you’re looking to seriously up your admin game. No web interfaces, lots of time in the terminal ( command line ) and more configuration files than is anyway reasonable. And we haven’t even started on virtual machines like proxmox ( also Debian based! ) or container critters like docker and kubernetes. (Iirc true nas uses kubernetes under the hood)
alt-text
___alt-text: The “I lied, I don’t have netflix” meme template. The girl with heavy dark rings around her eyes points a gun at the observer, with various images inserted in the background. The images include references to debian, libreboot, rsync, sed&awk, cron. The text reads: “I lied, I don’t have netflix - Take off your shoes, we’re going to learn to setup a NAS with Debian customized and automated to the bone and also automate the deployment process with Kubernetes. Everything will have 3-2-1 backups and controls will be networked to the volume slider in the radio of your car. We will use the motherboard of your calculator because it’s supported by libreboot.”
cool, then we can chill?
Small correction: since the newest version there only is Trunas Scale, so the Debian derivative, which they now call Community Edition. The BSD variant has been decommissioned as far as I know.
You seem like the right person to ask this:
What route do I go if I want to up my admin slowly so I eventually feel able to run pure Debian? Currently running Docker on Unraid with two minor VMs but looking to migrate away from Unraid with the intention to only run FOSS (and get a deeper understanding of everything under the hood).
I know that’s little information, all I need is a nudge in the right direction so I can figure things out by consulting documentation and forums.
Realistically, comfort comes from experience. The more you use it the more you’ll feel comfortable.
If you want to get a lot of exposure without dedicating too much time to it and limit the risk, I would say, spin up a Debian VM and try to configure it into the server you want the old school way. Setup ssh keys, raid pool and samba share all via ssh. Try to do it like you’re actually deploying it. This will give you real world exposure to the command line and the commands you’d run. Next maintain that server like it’s production, ssh in every couple of weeks to run updates and reboot. Just that muscle memory of logging in and reviewing updates will help you feel more comfortable. Do it again with another service (a VPN server would be an easy choice, a Minecraft server is also a fun one but requires a lot more memory. DNS would be good if you’re feeling brave, but that’s really just because DNS architecture is more complex than most realize) and maintain those servers too
Once you’ve setup a couple of servers and spent a couple of months monitoring and updating them your comfort level should be much higher and you might feel ready to setup some actually home production servers on Debian or the like.
You mentioned running Trunas and wanting to learn Debian and other FLOSS software, the easy button answer is to run Proxmox. Its free and open source with paid enterprise support plans available and has been rapidly improving just in the handful of years I’ve been running it. Proxmox is really just a modified version of Debian. They have some tweaks and custom kernels over stock Debian but impressively actually have a supported install method of installing overtop of an existing Debian install and apparently some Proxmox employees actually run it as their workstation operating system
I’ve actually been working my way through the proxmox-on-top-of-debian guide recently, but after installing the proxmox-ve kernel and rebooting, I was left with SSH disabled (connection refused) and no local console (more precisely no monitor output past “loading initial ramdisk”). I have so little time on my hands that troubleshooting is sometimes taking the fun out of it. Probably just going to re-install using the Proxmox ISO.
If you can afford it it’s a good idea to buy a Raspberry Pi since Raspbian is basically just debian. Then replicate your current setup on it and just try to tinker with it without any risks of breaking things or losing data.
If you’re using a lot of Docker I would recommend learning the command line since you’ll be able to use Docker on basically any real OS at that point.
Welcome to home labbing… you poor fool!
Honestly figuring out docker is 50% of the journey with the other 50% mostly being networking. For instance if your looking to start your own Jack Sparrow themed streaming service you’d want to grab a domain name, point it at your ip, open up ports 80 and 443 on your router, install a reverse proxy via docker and set up SSL ( hint: Caddy makes this easy ) and point it at your jellyfin docker container and voila, your very own streaming service you can access from anywhere! Notice the complicated part of all this is mostly the networking and docker setups, not so much the OS that your running. ( Note: don’t open ports without knowing the risks )
Debian is a fine OS but most homelab stuff can be done on anything you can install docker on, even on a windows computer! That’s not to say you shouldn’t learn some Linux server stuff but it isn’t wholly necessary. That being said…
My best advice for getting into Linux servers would be to grab an old PC, laptop or even a raspberry pi and install Debian, raspbian or any other distro on it. Figure out how to log in via ssh and get the thing running headless ( no keyboard or monitor ) and just learning to navigate and do things via the terminal. Some of the basics would be learning to use the package manager to install software, mounting the file system remotely and figuring out how to setup static IPs and such. When your ready go ahead and install docker, follow some tutorials, learn some yaml and your off to the races!