I was thinking about changing my server’s OS (currently using Ubuntu server)

Which would be the best in the case of only using docker and ZFS?

I thought that Debian would be more debloated and efficient but I need a Web UI and from what I have seen TrueNAS is very complete and is not absurdly slow, let me know your thoughts!

2 points

Truenas scale is Debian, if you just use it remotely it may be a good bet. If you may use the server as workstation (e.g. desktop) then you better use Debian itself (or both, as VMs under Proxmox). Managing ZFS is super easy, just create a couple of volumes with small and big blocksize, in either cockpit or whatever web ui. You may also switch OS (e.g. disaster or play around), and recover these effortlessly with zfs import command from CLI. Good luck!

permalink
report
reply
8 points

What do you need the webUI for? What’s the use case? Here are a couple for you:

For simple file management and sharing, you may use FileBrowser. It’s a single binary written in Go, just download and run.

If you’re looking for a more advanced and generic server management solution, then Cockpit is a good option. It’s available from Debian’s repositories and provides a UI to manage users, storage (including RAID), firewall, system services and even virtual machines. Can also manage Samba shares.

Cockpit uses the same system tooling you would use from the command line. You can switch back and forth between Cockpit and whatever else you like. It wont pollute your system like other solutions and there are dozens of extensions for it.

permalink
report
reply
1 point

I’ve beem using cockpit for years but it does not work with docker and some plugins (like the zfs one) have some assets missing, also the Navigator works really slow when moving files (it should be instantaneously) and leaves the empty folders in the old directory, making me always end up using ssh for that things.

I was thinking about using FileBrowser in a docker container but I would also like a UI for ZFS and basic graphics for system load. Htop and btop are some options but I don’t feel comfortable using them

permalink
report
parent
reply
1 point

some plugins (like the zfs one) have some assets missing, also the Navigator works really slow when moving files (it should be instantaneously) and leaves the empty folders in the old directory

I believe there’s something wrong with your setup then.

I was thinking about using FileBrowser in a docker container

Filebrowser is a SINGLE binary, no need to run it in a container and deal with all the mapping stuff when it would be an essential part of the NAS.

permalink
report
parent
reply
1 point
*

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters
LXC Linux Containers
NAS Network-Attached Storage
RAID Redundant Array of Independent Disks for mass storage
ZFS Solaris/Linux filesystem focusing on data integrity

4 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.

[Thread #569 for this sub, first seen 3rd Mar 2024, 20:25] [FAQ] [Full list] [Contact] [Source code]

permalink
report
reply
6 points

Don’t use TrueNAS for anything but a NAS

permalink
report
reply
9 points
*

TrueNAS is a propose built solution.

You’ll need to use it the way it’s designed, which is extremely capable, but reading the manual is mandatory or you’ll do it wrong and then it will suck. I know this.

There’s TN Core, and Scale. Ones based on FreeBSD, one’s Linux. You can compare for your needs.

TN can be an enterprise solution if that tells you the capability.

Edit, it’s meant to be a storage solution. Scale adds containers. It’s not great IMO as a general purpose server OS .

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.8K

    Monthly active users

  • 3.5K

    Posts

  • 79K

    Comments