Hello! I have Proxmox VE running on a Dell R730 with an H730. Proxmox manages the disks in a ZFS RAID which is exactly how I want it. Because I intend for this server to have a NAS/file server, I want to set up a container or VM in proxmox that will provide network storage shares to domain-joined systems. Pretty much everything in my lab is joined to FreeIPA, so I’d like to use the IdM features with my file server. I have given TKL FileServer a shot but it really didn’t seem up to snuff with what I wanted. I am not looking for a NAS solution that will require me to pass through the RAID controller and disks to Proxmox, as I want Proxmox managing the ZFS pool. I can set up an NFS/Samba server in a container, however in trying to do so I was running into issues (due to it being an unprivileged container) that I can probably figure out but I want to see if anyone has any recommendations first.
Hmm. If you are going to have proxmox managing zfs anyway then why not just create datasets and share them directly from the hypervisor?
You can do that in terminal but if you prefer a gui you can install cockpit on the hypervisor with the zfs plugin. It would create a separate web gui on another port. Making it easy to create, manage, and share datasets as you desire.
It will save resources and simplify zfs management operations if you are interested in such a method.
I do it the other way round: proxmox leaves it’s hands away from the zpool. The 5 disks are passed through to a vm, everything ZFS starts there, and it offers the samba shares.
My directive is that the bare metal proxmox shall not offer any services to the world outside, only VM’s may do that.
My go-to for this is a plain Debian or Ubuntu container with Cockpit and the 45Drives file sharing plugin. It’s pretty straightforward and works pretty well.
Probably not best practice, but it’s possible to install it on the PVE host itself since its ZFS manager and Identity manager plugins and other features fills some gaps in what Proxmox doesn’t do (or would have to drop to CLI to do).
Also recommend RClone in a systemd can take care of various file movements, syncs and backup tasks you may need against the host, vdumps or SMB file shares.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Hmm. If you are going to have proxmox managing zfs anyway then why not just create datasets and share them directly from the hypervisor?
You can do that in terminal but if you prefer a gui you can install cockpit on the hypervisor with the zfs plugin. It would create a separate web gui on another port. Making it easy to create, manage, and share datasets as you desire.
It will save resources and simplify zfs management operations if you are interested in such a method.
i think I’ll give that a shot
I do it the other way round: proxmox leaves it’s hands away from the zpool. The 5 disks are passed through to a vm, everything ZFS starts there, and it offers the samba shares.
My directive is that the bare metal proxmox shall not offer any services to the world outside, only VM’s may do that.
My go-to for this is a plain Debian or Ubuntu container with Cockpit and the 45Drives file sharing plugin. It’s pretty straightforward and works pretty well.
Seconded on Cockpit project w File Sharing.
Probably not best practice, but it’s possible to install it on the PVE host itself since its ZFS manager and Identity manager plugins and other features fills some gaps in what Proxmox doesn’t do (or would have to drop to CLI to do).
Also recommend RClone in a systemd can take care of various file movements, syncs and backup tasks you may need against the host, vdumps or SMB file shares.