A few updates since Debian 12 (Bookworm) released: -You don't need to add the backports repo, Bookworm includes the more updated packages -You don't need to specify the backuports repo in apt install cockpit -Make sure your group is the owner of your data directories and you have permissions to read/write by group (default is by user).
How do you make the group the owner of the data directories? I tried to do this but it wont give me the option to choose the group that I made. The error message I get is: "changing group of '/mnt/data/': Operation not permitted"
@@chrisrgutierrez I think what he means here is set the group ownership of the directory to the group you created. You can leave the user ownership as 'root' or whatever user it already is. But then make sure the group has full read, write, execute permissions. So if you run ls -la you should see "drwxrwxr-x" instead of "drwxr-xr-x" which is the default. In other words: 1. use chmod to change the directory permissions to 775, then 2. use chgrp to change the group ownership to whatever group you created. That's what fixed it for me. Hope it helps!
Update for ProxMox 8.1.x and Debian 12 - when you create your Linux Container (LCX) make sure you enable "Nesting" in the options screen before starting it. Removing the "Unprivileged" flag no longer allows "nesting" by default, and you'll run into all sorts of issues. Hope this helps!
This is bad-ass. And your delivery is not annoying at all. Straight to the point, no bs. I just followed this video to setup samba on a Dell T320 I'm giving to a friend who wants to learn linux, proxmox, and zfs at the tender age of 75. Subscribed and thank you!
Also, I appreciate how you don't have a long music/special effects intro. No one cares about that stuff. Also... 91MB of RAM for a NAS container. How cool is that??
I've been tearing down my homelab vSAN in favor of Proxmox. I had been using a VM as a file server was thinking about simplifying and deploying a samba container. I hadn't even considered Cockpit. Thanks for the great content!
thanks for the tutorial, helped me out a lot! As a side note, at first i was read only limited on the windows side, turns out i had to go back to file sharing in cockpit and edit the permissions of my shares path to use the newly created user and group to either be the owner or add write permissions to the newly created group.
Thanks you so much for this. This secret lies under File Sharing / [YourShare] / Path / Edit Permissions (faded colour) so it was not something obvious to find.
Awesome video! I've been agonizing over the question of running truenas on bare metal or virtualizing through proxmox. This seems like a great solution!
I've been literally twice to this channel from a seach (different searches). Have not been disappointed in both occasions. Got my sub man. Great work and direct with great extra comments between steps.
thx for the clear, short tutorial. No ads, no fancy talk, just all what the home/hobby users need. I used Webmin and manual smb edit, but your video helped a lot too. My side notes: watch out for backup flag at PVE mount. If you create a shared backup HDD inc. PVE shares -like I did- the backup flag is a mistake... :)
Aweome work! Would love to see the following configuration in your future videos: - 2 disk NAS - 1st main SSD fast - 2nd the one for backing up the first (e.g. once a day) or raid (but honestly raid isn't worth it with limited drives, at least imo) - Additionally, a way to backup everything related to Proxmox (incl. Proxmox host & VM/C) on the NAS, so in case that main disk fails, you'll have a way to restore your setup.
Great video! It's the little explanations that I really enjoy. Like lxc and kernal relationship and that it's a quota rather a dedicated amount of resource.
- create an new VM in Proxmox - allows easy pass-through of USB drives - install Debian 12, maybe with LUKS encryption - sudo apt install nfs-kernel-server ufw ufw-extras - sudo ufw enable - sudo ufw allow nfs - sudo nano /etc/exports - edit to your needs, using the infos provided in the opened file as a template. - mount the share from anywhere you want and use it as a network drive. Only Windows needs some additional software to mount the share, but there are good open source solutions.
WOw, this was an incredible tutorial. Really neat to see what you are going to do with that small fileserver. Never thought about wiping the NAS and putting Proxmox on it. Brilliant !!!
My man. I have been struggling with getting TrueNas or OMV running on proxmox, but setting up the mount points always killed me. Your video showed me I don't even need either of those to be functional. Thank you!
Something I had to do which differs, this may be just because of how I set my drive up in Proxmox, etc. But after I created the share, I had to go back and Edit Permissions. and I had to check write for Group to be able to actually create a directory, file, etc. from a remote system accessing a share, In this case both Windows 10 and Ubuntu... I think 22.04. cant remember, getting old, lol And if you have trouble with a FSTAB mount in Linux using cifs try using vers=2.0. I had been using 1.0 for some older shares on legacy systems and had just copy/paste to the new line for this share mount.
Fantastic tutorial, straight to the point, perfectly explained what each option actually means. After watching tons of tutorials on setting up a classic Samba share, this one is by far the best explanation. The setup in other tutorials with Debian and then another Debian inside Debian feels like Inception. You’ve definitely earned a new sub!
"That just seems dumb." Is exactly the thought I had when thinking about virtualizing Truenas and passing through my 4 drives. Such an unnecessary layer of overhead and complexity. This video arrived at the right moment for me. Have been looking at different options for storage and think I'll give this a try. Whats the process for creating NFS shares through this?
NFS is ... a lot more tricky than Samba, since it's normally managed via the kernel server. Since the container is in its own namespace, even a privilaged container can't control the kernel's nfs exports. You can disable all isolation of the container and then it will work, but this is strongly not recommended. The solution is to use nfs-ganesha (userspace NFS server), but Cockpit doesn't have a GUI module for that. TrueNAS also uses nfs-ganesha, incidentally.
In general I use SMB over NFS in my own setups since Windows access is important. But, fundamentally, NFS and SMB are quite different protocols in how they deal with user permissions and access, and SMB is easier to administer due to server-side account permissions. As to performance, SMB can achieve roughly the same performance as NFS on large file IO and is dramatically slower on small file IO. For videos, SMB is perfectly adequate.
Except it's not dumb lol. Backing up and managing file shares, permissions etc from Proxmox is a headache. A separate VM that you can snapshot and pass through a HBA or controller is a much better idea.
Also, not everyone may wanna buy an enterprise grade ssd to deal with write amplification of zfs. So you use proxmox with lvm in a consumer ssd (speed benefit without huge write amplification of zfs) and then have a virtual truenas combining multiple hdds in a zfs pool (say in a raid 10 array).
This has transformed proxmox for me (which in itself is a great hypervisor, but not a very practical NAS OS by design). Thank you for a very coherent and informative tutorial, that I was able to tweak to my preferences on the go. I'll certainly check out your other tutorials. Keep up the great work.
I have been binge watching your videos and thinks to you I have reinstalled my proxmox servers a few times now to get it just right an of course to learn. My head still hurts after watching your Nebula video. In my case I had a 16GB drive I wanted to connect a proxmox server and then use your cockpit method to share the contents to the internal network. To do that I used lsblk to identify the NTFS partition and then created a mount point on the proxmox server in /mnt/pve and mounted the disk. After a bit of digging I found the command to share a mount point to an LXC and it worked! Here is what you need: pct set 103 -mp0 mp=/host/dir,/container/mount/point. Just remember to edit fstab afterwards. Thanks for your great tutorials!
Thanks for the great video! Hopefully this will satisfy my needs for a file share without having to run a nested virtual server or separate hardware server!
Thank you for the tutorial, of all the options I tried, this one works best for me, much simpler to use compared to Turnkey and File Server, and the fact that I can import old configuration is amazing.
Thank you, this was great. Took me 2 hours total to set everything up including debugging and learning some beginner steps that you (reasonably) skipped over. I now have a working NAS! So happy.
Exactly the tinkering distraction I was looking for so I don't need to deal with the pile of real work I need to be doing. Great instructions and thank you for giving me something to do today other than work! lol
I've made some additional discoveries. So. I am not running IPV6 on my home network at the moment. And as such it is taking the DHCP request ~5 minutes or so for that to timeout before the container will finish starting up. I was able to disable this in the container itself. in the container edit /etc/sysctl.conf and add a line that says "net.ipv6.conf.all.disable_ipv6=1" without quotes and then reboot the container. You can do the same for the entire PVE system by doing the same but in the proxmox base system. The way I did it just modified the individual container.
Did you set the IPv6 address to DHCP in Proxmox? Setting it to static and leaving it empty will cause it to not assign an IPv6 address at all (other than the link local address).
@@apalrdsadventures I can't recall if I tried that or not. Might be worth trying to spin up another one and see if it lets me select static and leave the boxes empty. Some software requires you to populate it. Not sure about PVE
Very nice, i am getting inclined to switch my home server over to proxmox. I was thinking about this before, just because LXC. So much less overhead than a full VM. And docker is a mess after some time (TM). Really appreciate your focus on small home labs/server. Most stuff about this is "look at this (insert expensive hardware)", which is not what most home servers owners have access to.
I've to agree. Simple fast and convenient. I'm rocking tow 2nd hand HP Micro Servers, 40 and 50 models. First time seeing this tut I has really septic about it's practical use, but after consecutive Trunas Core VM and containers unexplainable failures (in my Proxmox environment), I decided to opt take in consider that my hardware and my resources would better function with a similar scenario. Sharing is caring, an thank you for sharing your thoughts whit us. Cheers from Portugal ;)
Thanks for the guide! As a lot of people in the comments, I was also considering true as/unRAID in bare metal or on a próximos VM. This makes a lot of sense, will definitely try that out! Thanks
Excellent video! I always appreciate the great Proxmox content you put out. Also, I hadn't heard of Cockpit before so I appreciate learning about that as well. I'll definitely be using it from now on.
I did something similar directly on one of my Proxmox nodes to share an attached (not ZFS) disk for backups, but using WebMin instead of Cockpit for the SMB setup. My next project is to convert an old desktop into a NAS, but I still wanted to stick with ProxMox, and give it a couple proper ZFS pools (SSD and rust, similar to yours), but I didn't want to do the SMB/NFS install on the bare metal hypervisor again, so I'll definitely be "borrowing" your LXC + Mount Point idea 👍👍
Super helpful tutorial!! You may already have a follow on video or article about this, but I think it's important to create an admin account as part of this setup. One that is not root so that you can remove root from being able to login via GUI. In order to do this you'd want to create a new admin user and then add them to the sudo group. Then when that user signs into cockpit they can click this "Limited access/Admin access" toggle at the top of the page.
I more or less did the same thing. Except I used a privileged container so I could export NFS. The tricky thing with storage is user accounts. Your NAS has to have user accounts for everyone and in the case of NFS those UIDs have to match the client machine UIDs. You can share things straight off of PVE, but that would require you add all your actual users and credentials to PVE which feels wrong. The idea I had was to put all the storage through that one NAS container and use it to share disks to the other VMs/CTs. That gets a bit broken because PVE is a bit fussy about what storage your can write what to, so you end up mapping a filesystem into the NAS container and then mounting the NFS share back on the PVE host. Which also feels wrong.
I think it would be interesting to do similar walkthrough for NFS (next to your SMB setup) and go into details on how it should be used as shared storage for other Proxmox nodes and VMs running on external nodes (should we use VLANS to segregate node and VM traffic? Or is NFS IP based security enough? NFS version? root squash? etc)...and I was also curious about the performance of this mounted NAS/NFS running under Proxmox LXC/VM vs. Disk Passthrough to VM vs. the Native NAS/NFS performance.
NFS is a bit of a different beast to manage, since usually you'd normally use the kernel server. nfs-ganesha is a userspace nfs server which would work in a container. For performance, Samba runs in userspace and the host ZFS pool is bind mounted into the container, so performance in an LXC will be the same as native until it hits a resource limit (either CPU or RAM). For NFS, performance using nfs-ganesha should be worse than the kernel server, however, TrueNAS uses nfs-ganesha anyway.
@@apalrdsadventures Haha, yeah, I ran into that today. To do NFS, you have to make it a privileged container and enable NFS in the features ... that said, I am also running into multiple failures when trying to get it running. When doing it in an unprivileged container I get dependency errors starting the nfs-server. When I do it in a privileged container I get errors starting the cockpit service. Any thoughts?
Ah, great method! I've already built something up using an OpenMediaVault VM over Proxmox bc I wanted that GUI with solid user management/permissions, but I like the container/cockpit method a lot.
This is perfect for my needs, thanks for making and sharing this information mate! Now I'm motivated to build a small backup server, to make weekly backups of the proxmox 'nas' files for long-term protection. Cheers!
I took a different approach to moving my TrueNAS data to Proxmox. I just installed Samba, NFS and WSDD on Proxmox host directly and use it's user management. Yes I still have to manage shares by via cli but I'm fine with that. Network browsing works, previous versions works (via ZFS snapshots) and even have recycle bin working via Samba.
But if you lose the host OS/hardware, then you can't "simply" restore Proxmox to a new host without manually reinstalling all the extras you have added. Putting all the extras in a LXC container means they could be easily restored from (ie;) Proxmox Backup Server.
Thanks for releasing this video! While I'm not Jellyfin'ing, the LXC tip to enable hardware Quick Sync Video worked wonders with Channels DRV on a Intel Xeon E3-1265L powered Proxmox setup. Also the Terramaster Intel NAS looks pretty sweet, keeping an eye on that one! Thanks again!
I am running proxmox (pimox) on an orange pi 5 with a 2TB nvme. 2 VM's, 5 LXC, it is enjoying itself at 6 Watt with some load, runs great. Cockpit looks useful, wil give it a shot. I use Alpine for the VM's and containers, it is like 30MB lol although that is quite barebone.
Just as a heads up for anyone having issues running this in a privileged container you must enable nesting by adding features: nesting=1 to the container .conf before the cockpit webgui will come up.
I didn't realize Proxmox lets you add container mountpoints on its own storage pool. That opens up so many more possibilities. Now I wonder why they don't do the same for the container's root filesystem, that would make so much more sense to me.
You can add mountpoints to the host's storage as well (using pct set --mpX to create bind mounts), but in this case Proxmox's storage backend for ZFS implements container mounts as native zfs datasets. Not all backends do this, some will create separate filesystems.
The GUI will create managed mountpoints on any storage backend that supports containers, for some (like ZFS) it uses native datasets and for others it will create a filesystem backed by a file. From the command line you can also use pct to create mount points which refer to a path in the Proxmox host, which can include all of the file-based storage paths (like smb / nfs). pct is the command for this, and qm is for VMs.
@@apalrdsadventures Nice... the bind mounts work to export cephFS via cockpit/SMB, too (no smbmodule) ...my new erasure pool is filling up since yesterday - waiting for the 4GB RAM thin-client-2TBnvme-OSDs to OOM now ;D...PS: It's not always "dumb" to run Truenas in a VM - in my case the ZFS pool was still from the Freenas days - the host was converted from baremetalNAS with jails to pve+VM ... and it worked for years.... Thanks for the video have a great weekend!
@@apalrdsadventures If I create a mount point within the gui (example 100GB) the mount point will be generated (new folder) on my storage, and it is included within my backup. But if I add an existing folder (which can use all of my hdd space) with all my data as mount point. This mount point is not included within the backup. Is there an work around to add existing folders or even new folders (without setting a size) wich will be included within the backup?
I'm slowly getting there, I started with just the features that Proxmox exposes through the GUI, now there's a little bit of manual dataset creation, but zpool management is another thing
WHAT HAVE YOU DONE? Now i must tear up my system and replace my truenas in proxmox with this solution. Do you know how much work you have caused me !?!?!?! But jokes aside, great vid
Ok, this ended up being a nightmare for me to setup (likely due to a vast amount of inexperience) Here are some of the modifications I had to do to get everything working: 1. Use the Debian 12 template instead of 11. 2. Do NOT modify the sources.list, because Debian 12 already has access to the new Cockpit 3. Instead of giving access to the entire mounted drive, make a subfolder, and give access to that instead. 4. Grant access to the group using chown -R :my-group-name /my/file/directory 5. Grant access to the user using: chown -R my-user /my/file/directory Is this reasonable/correct? I have no clue, but it worked for me. Idk if using chown is a bad security practice or not. Other notes: If you do not have a disallowed-users file, it is because you are using an older version of cockpit. You either are not on Debian 12 or did not install from the backports repo (if on Deb 11)
Excellent video!! There is also an option with Turnkey that has Samba pre-installed and pre-configured. Have you tried that? and what are the disadvantages compared with the Cockpit approach?
I tried Turnkey fileserver first, found that the GUI wasn't as good as Cockpit, the Webmin-based manager has a ton of options to manage services on the system that shouldn't be managed in an appliance (like Apache settings, or hostname / network which are managed by Proxmox), and it doesn't natively support IPv6. Cockpit is also lighter weight than running Apache and runs itself as the logged in user.
I'd love a Proxmox tutorial on using LVM to have a pool of disks I can add to & remove from which can be mounted as a single logical volume on /mnt/storage then passed through/shared by multiple containers (TurnKey SMB or Cockpit, Deluge, Plex, etc). My use case is setting up a non-critical home NAS with a bunch of drives I have lying around. I can't use zfs raid due to the varying disk types/sizes and the desire to add/remove drives over time (I think zfs raid5/6 will limit the size to the smallest drive in the array and you're limited to 5 drives?). I'm thinking that the flexibility of LVM means that I could set alerts on SMART warnings and simply remove/replace a disk if it looks unhealthy somewhat mitigating the need for redundancy - but worst case scenario I _think_ LVM doesn't drop the whole disk array if a single physical disk dies, only the data on that drive meaning I can pair a 1TB SSD next to an 8TB HDD without worrying too much that the 8tb would get dropped if the SSD fails. So far I've tried creating a logical lvm volume from a pool of disks however mounting them makes them show up as 100% used in Proxmox (though I don't know what that actually means). Haha, maybe I should have bought an off the shelf NAS rather than try to DIY it. halp pls
Does anyone else have relatively high CPU usage for cockpit processes when setting up this way? Was consuming around 20-25% CPU on my Terremaster/Proxmox, even with nothing going on. I ended up stopping the cockpit service and just running plain old samba by itself. I also had to set this up as a privileged container so it had read/write access to the shares. This also required bind mounts of the ZFS datastores from the Proxmox host to the container. Nothing I could do would allow even local users to write to the mounts local to the containers or the shares. But all is running now and I like this a lot better than my prior attempt at passthru to TrueNAS in a VM. Thanks apalrd for the idea!
I'm not sure why Cockpit is using so much, it shouldn't have any long-running processes since it uses systemd socket activation. As to permissions, unprivileged containers have an offset user id / group id in the host (root in the container is uid/gid 100000 on the host) so bind mounting from host to container you'll need to either chown to the guest's uid or gid, or chmod in a way that the guest has access. Privileged containers don't have the uid/gid offset.
Followed guide, everything was working great except transferring large files (14GB and larger), one or two large files might copy but the container would always lock up or samba within the container would crash. Increasing the memory from 1/2 GB to 8 GB fixed all issues. FYI this is on a 10gb (RJ45) network
I have an issue with logging in. I can log into the proxmox lxc debian console, but I can't log into the web ui. I can still access all the shares I setup through cockpit though.
I have followed along with this guide and your jellyfin guide. My fileserver is "unprivledges" while the jellyfin is priveledged container. I used the manual steps to add mount points to both. The problem is on the unprivledged container the ownership of the mount is nobody and nogroup because the root has a differnent UID I think. And I can't change the permissions on the fileserver
I have a weird issue. Cockpit keeps using up about 20% of my available CPU power after following this guide. Cockpit is obviously trying to do something I just have no idea what. I've taken to manually turning cockpit on/off using systemctl whenever I need to log in but I'm hoping to find a solution to this problem... Apalrd, this is a great guide and series. Thanks for putting it together it has helped me quite a bit!
I flailed around in Proxmox for a day before installing TrueNAS, shouldve watched this video. Definitely agree that the "just run TrueNAS with passthrough" advice seems really unsatisfying.
There should be a way to map it to a Windows machine from outside the network. That way, if you're on vacation or something, you can access files or perhaps offload pictures from say your phone to a laptop that has the mapped "drive".
I have a running setup thanks to you're video. Now I would like to implement syncthing in this. But I can't yet seem to get this to work like I think it should. Backup/Sync from cockpit shares to backup NAS share. Do you have any experience with this? Or maybe this is an Idea for a next video?
I was always wondering why everybody is installing TrueNAS on Proxmox for filesharing and ZFS when proxmox has the same funcionality. There is no need to passthrough Sata controlers, PCI-e and waste resources for another OS which can do the same thing what proxmox can do... TrueNAS is great (except that it doesnt allow to use SDD which its installed for anything and literally wasting SSD). In proxmox there is turnkey fileserver LXC template which automatically makes filesharing works on proxmox.
I did try the turnkey LXC before setting this up and was not happy with it compared to Cockpit. I found the UI to be worse than Cockpit, Webmin includes management of a lot of things that shouldn't be touched (such as apache2 which runs the turnkey GUI, and hostname / networking settings which Proxmox overwrites), cockpit runs as the logged in user and inherits their permissions from the Linux system instead of doing its own user management and security, and Turnkey didn't deal with IPv6 properly out of the box.
So pleased to have found your channel. Is there an LXC container manger (like exists within Proxmox) for Cockpit or some other? I see it can do VMs and I'm already familiar with Virt-manager. I'd like to just run Debian with a gui desktop, kvm-qemu, LXC containers and Docker within one of those too but also be able to access and work at the machine itself. I see Incus is coming with Trixie. Not sure about LXD now that it's getting dropped after bookworm?
Nice! proxmox ui seems like the best. without an add on card I don’t have the ability to pass thru my hdd to truenas vm. now to set up hand break and makemkv containers and have them have access to those storages.
@@apalrdsadventures you do for Truenas to give direct disc access, but your method that I'm trying now will omit truenas. Just wondering if I'll miss any better zfs perks of truenas?
Thank for the video, this convinced me to migrate from virtualized truenas to this way, BUT can you explain the drop of perfomance? truenas used to be much faster
What performance difference are you seeing? TrueNAS (SCALE) should have very similar zfs tuning to Proxmox VE, but if you are coming from CORE you will have less ARC space.
![ร้อยพ่อพันแม่ - WanMai [Official MV]](http://i.ytimg.com/vi/XY2pNYASEbg/mqdefault.jpg)
![ลองสุ่มไอโฟน 990 โกงมั้ย? [ โกงมั้ยครับ ep.101 ] | DOM](http://i.ytimg.com/vi/bfsWe0j492k/mqdefault.jpg)
A few updates since Debian 12 (Bookworm) released:
-You don't need to add the backports repo, Bookworm includes the more updated packages
-You don't need to specify the backuports repo in apt install cockpit
-Make sure your group is the owner of your data directories and you have permissions to read/write by group (default is by user).
How do you make the group the owner of the data directories? I tried to do this but it wont give me the option to choose the group that I made. The error message I get is: "changing group of '/mnt/data/': Operation not permitted"
did you figure this out? im pretty new to this stuff @@chrisrgutierrez
@@chrisrgutierrez I think what he means here is set the group ownership of the directory to the group you created. You can leave the user ownership as 'root' or whatever user it already is. But then make sure the group has full read, write, execute permissions. So if you run ls -la you should see "drwxrwxr-x" instead of "drwxr-xr-x" which is the default.
In other words:
1. use chmod to change the directory permissions to 775, then
2. use chgrp to change the group ownership to whatever group you created.
That's what fixed it for me. Hope it helps!
@@chrisrgutierrez seems your currently used user is not root (as in the tutorial) or not part of the of sudoers?
@@chrisrgutierrez the version I am using (logged in as root) I see edit permissions under the path (mount point)
Update for ProxMox 8.1.x and Debian 12 - when you create your Linux Container (LCX) make sure you enable "Nesting" in the options screen before starting it. Removing the "Unprivileged" flag no longer allows "nesting" by default, and you'll run into all sorts of issues. Hope this helps!
I don't see this. Please elaborate.
cool mate. Your best feature is your ability to describe what you are doing and why you are doing it. appreciated.
This is bad-ass. And your delivery is not annoying at all. Straight to the point, no bs. I just followed this video to setup samba on a Dell T320 I'm giving to a friend who wants to learn linux, proxmox, and zfs at the tender age of 75. Subscribed and thank you!
Also, I appreciate how you don't have a long music/special effects intro. No one cares about that stuff. Also... 91MB of RAM for a NAS container. How cool is that??
I've been tearing down my homelab vSAN in favor of Proxmox. I had been using a VM as a file server was thinking about simplifying and deploying a samba container. I hadn't even considered Cockpit. Thanks for the great content!
Glad I could help!
thanks for the tutorial, helped me out a lot!
As a side note, at first i was read only limited on the windows side, turns out i had to go back to file sharing in cockpit and edit the permissions of my shares path to use the newly created user and group to either be the owner or add write permissions to the newly created group.
Thank you! You just solved my problem!
Thanks you so much for this. This secret lies under File Sharing / [YourShare] / Path / Edit Permissions (faded colour) so it was not something obvious to find.
Thank you so much for this! My share only had permissions for root until I made this change.
You have a gift for simple but deep explanation. Great work
Thanks for bringing up the Cockpit project. It will be a good addition to my Proxmox-NAS hybrid which I have been admining via CLI👍
It's a pretty useful project, and the GUI is low-resource and looks good
Awesome video! I've been agonizing over the question of running truenas on bare metal or virtualizing through proxmox. This seems like a great solution!
Glad it was helpful!
I've been literally twice to this channel from a seach (different searches). Have not been disappointed in both occasions. Got my sub man. Great work and direct with great extra comments between steps.
thx for the clear, short tutorial. No ads, no fancy talk, just all what the home/hobby users need. I used Webmin and manual smb edit, but your video helped a lot too. My side notes: watch out for backup flag at PVE mount. If you create a shared backup HDD inc. PVE shares -like I did- the backup flag is a mistake... :)
Aweome work! Would love to see the following configuration in your future videos:
- 2 disk NAS
- 1st main SSD fast
- 2nd the one for backing up the first (e.g. once a day) or raid (but honestly raid isn't worth it with limited drives, at least imo)
- Additionally, a way to backup everything related to Proxmox (incl. Proxmox host & VM/C) on the NAS, so in case that main disk fails, you'll have a way to restore your setup.
Great video! It's the little explanations that I really enjoy. Like lxc and kernal relationship and that it's a quota rather a dedicated amount of resource.
Fun fact, linux cgroups (the method for enforcing quotas) can also be used to limit the CPU/RAM of individual user accounts, it's super handy
You are a god send. This is now my favorite Proxmox guru channel. Not sure exactly why, but this was a pleasure following along.
That is exactly what I was looking for, the perfect alternative to TrueNAS and OMV for sharing. Thanks for your videos.
- create an new VM in Proxmox - allows easy pass-through of USB drives
- install Debian 12, maybe with LUKS encryption
- sudo apt install nfs-kernel-server ufw ufw-extras
- sudo ufw enable
- sudo ufw allow nfs
- sudo nano /etc/exports
- edit to your needs, using the infos provided in the opened file as a template.
- mount the share from anywhere you want and use it as a network drive. Only Windows needs some additional software to mount the share, but there are good open source solutions.
Great video. Thank you. I've been using Proxmox and TrueNAS for a while and just installed Cockpit today. Perfect.
nice. do you use truenas like vm into proxmox?
@@orafaelgf TrueNAS as Proxmox storage
WOw, this was an incredible tutorial. Really neat to see what you are going to do with that small fileserver. Never thought about wiping the NAS and putting Proxmox on it. Brilliant !!!
My man. I have been struggling with getting TrueNas or OMV running on proxmox, but setting up the mount points always killed me. Your video showed me I don't even need either of those to be functional. Thank you!
Glad it's helpful!
Your videos are amazing! Probably the best tutorials on TH-cam in the self-hosting space. Thank you for doing what you do!
Glad you like them!
Something I had to do which differs, this may be just because of how I set my drive up in Proxmox, etc. But after I created the share, I had to go back and Edit Permissions. and I had to check write for Group to be able to actually create a directory, file, etc. from a remote system accessing a share, In this case both Windows 10 and Ubuntu... I think 22.04. cant remember, getting old, lol
And if you have trouble with a FSTAB mount in Linux using cifs try using vers=2.0. I had been using 1.0 for some older shares on legacy systems and had just copy/paste to the new line for this share mount.
Fantastic tutorial, straight to the point, perfectly explained what each option actually means. After watching tons of tutorials on setting up a classic Samba share, this one is by far the best explanation. The setup in other tutorials with Debian and then another Debian inside Debian feels like Inception. You’ve definitely earned a new sub!
"That just seems dumb." Is exactly the thought I had when thinking about virtualizing Truenas and passing through my 4 drives. Such an unnecessary layer of overhead and complexity. This video arrived at the right moment for me. Have been looking at different options for storage and think I'll give this a try. Whats the process for creating NFS shares through this?
NFS is ... a lot more tricky than Samba, since it's normally managed via the kernel server. Since the container is in its own namespace, even a privilaged container can't control the kernel's nfs exports. You can disable all isolation of the container and then it will work, but this is strongly not recommended.
The solution is to use nfs-ganesha (userspace NFS server), but Cockpit doesn't have a GUI module for that. TrueNAS also uses nfs-ganesha, incidentally.
In general I use SMB over NFS in my own setups since Windows access is important. But, fundamentally, NFS and SMB are quite different protocols in how they deal with user permissions and access, and SMB is easier to administer due to server-side account permissions.
As to performance, SMB can achieve roughly the same performance as NFS on large file IO and is dramatically slower on small file IO. For videos, SMB is perfectly adequate.
i did truenas with EXSi. Truenas don't play well when it is a VM. in fact it corrupt data quite often.
Except it's not dumb lol. Backing up and managing file shares, permissions etc from Proxmox is a headache. A separate VM that you can snapshot and pass through a HBA or controller is a much better idea.
Also, not everyone may wanna buy an enterprise grade ssd to deal with write amplification of zfs. So you use proxmox with lvm in a consumer ssd (speed benefit without huge write amplification of zfs) and then have a virtual truenas combining multiple hdds in a zfs pool (say in a raid 10 array).
Fantastic, easy to follow even for a linux & proxmox newbie like me, thanks.
Even managed to connect to it with music assistant in Home Assistant
This has transformed proxmox for me (which in itself is a great hypervisor, but not a very practical NAS OS by design). Thank you for a very coherent and informative tutorial, that I was able to tweak to my preferences on the go. I'll certainly check out your other tutorials. Keep up the great work.
I have been binge watching your videos and thinks to you I have reinstalled my proxmox servers a few times now to get it just right an of course to learn. My head still hurts after watching your Nebula video. In my case I had a 16GB drive I wanted to connect a proxmox server and then use your cockpit method to share the contents to the internal network. To do that I used lsblk to identify the NTFS partition and then created a mount point on the proxmox server in /mnt/pve and mounted the disk. After a bit of digging I found the command to share a mount point to an LXC and it worked! Here is what you need: pct set 103 -mp0 mp=/host/dir,/container/mount/point. Just remember to edit fstab afterwards. Thanks for your great tutorials!
Thanks for the great video! Hopefully this will satisfy my needs for a file share without having to run a nested virtual server or separate hardware server!
Thank you for the tutorial. I was able to set up my Network Share successfully by following this guide.
Glad it helped
Thank you for the tutorial, of all the options I tried, this one works best for me, much simpler to use compared to Turnkey and File Server, and the fact that I can import old configuration is amazing.
Thank you, this was great. Took me 2 hours total to set everything up including debugging and learning some beginner steps that you (reasonably) skipped over.
I now have a working NAS! So happy.
Did you get a error when clicking on the file sharing plugin "ProcessError (exited non-zero)"?
@@arunforlife7009 No, I did not.
Exactly the tinkering distraction I was looking for so I don't need to deal with the pile of real work I need to be doing. Great instructions and thank you for giving me something to do today other than work! lol
Glad it was helpful!
I've made some additional discoveries. So. I am not running IPV6 on my home network at the moment. And as such it is taking the DHCP request ~5 minutes or so for that to timeout before the container will finish starting up. I was able to disable this in the container itself. in the container edit /etc/sysctl.conf and add a line that says "net.ipv6.conf.all.disable_ipv6=1" without quotes and then reboot the container. You can do the same for the entire PVE system by doing the same but in the proxmox base system. The way I did it just modified the individual container.
Did you set the IPv6 address to DHCP in Proxmox? Setting it to static and leaving it empty will cause it to not assign an IPv6 address at all (other than the link local address).
@@apalrdsadventures I can't recall if I tried that or not. Might be worth trying to spin up another one and see if it lets me select static and leave the boxes empty. Some software requires you to populate it. Not sure about PVE
@@Trains-With-Shane Just select SLAAC as you IPv6 method and you are good to go. SLAAC is in effect an automatically assigned static IP.
Very nice, i am getting inclined to switch my home server over to proxmox. I was thinking about this before, just because LXC. So much less overhead than a full VM. And docker is a mess after some time (TM). Really appreciate your focus on small home labs/server. Most stuff about this is "look at this (insert expensive hardware)", which is not what most home servers owners have access to.
I do enjoy making lower end hardware work for me, spending more time getting the software right rather than throwing hardware at it.
@@apalrdsadventures and truth be told - most home server users have old/repurposed hardware. I wish you much success!
Thanks!
Thank you for this simple walkthrough. been looking for a simple solution to integrate my NAS into proxmox.
Glad you like it!
That's actually a really pretty and creative way to do that stuff! Thank you for that inspiration!
I've to agree. Simple fast and convenient.
I'm rocking tow 2nd hand HP Micro Servers, 40 and 50 models.
First time seeing this tut I has really septic about it's practical use, but after consecutive Trunas Core VM and containers unexplainable failures (in my Proxmox environment), I decided to opt take in consider that my hardware and my resources would better function with a similar scenario.
Sharing is caring, an thank you for sharing your thoughts whit us.
Cheers from Portugal ;)
Greetings from Michigan :) Glad you enjoyed it
This is an excellent tutorial! I have been looking into building a simple file server for my home network!
Thanks for the guide! As a lot of people in the comments, I was also considering true as/unRAID in bare metal or on a próximos VM. This makes a lot of sense, will definitely try that out! Thanks
Glad I could help!
Thanks dude, got me where I needed to be. Simple and easy.
Oh man, apalrd. I'm doing this very project as we speak. Impeccable timing!
Hopefully it works well for you then
Thank you for the tutorial, very nice!
Excellent video! I always appreciate the great Proxmox content you put out. Also, I hadn't heard of Cockpit before so I appreciate learning about that as well. I'll definitely be using it from now on.
I’ve subscribed your channel because of this video alone. It is exactly what i was looking for! Thanks bro!
Nice work :) Had to add a bit of custom samba conf to get time machine working on the SMB share, but it works :D
Hey, this was pretty good. Fast and fluid w/o bunches of cuts. Nice + thanks!
Thank you so much! just got done with the video and everything just works very well made and easy to understand tutorial
Great to hear!
one of the best i have found on the interwebs
Thank you!
I did something similar directly on one of my Proxmox nodes to share an attached (not ZFS) disk for backups, but using WebMin instead of Cockpit for the SMB setup. My next project is to convert an old desktop into a NAS, but I still wanted to stick with ProxMox, and give it a couple proper ZFS pools (SSD and rust, similar to yours), but I didn't want to do the SMB/NFS install on the bare metal hypervisor again, so I'll definitely be "borrowing" your LXC + Mount Point idea 👍👍
Glad you like it!
this is exactly what I was looking for. I am going to try it out.
This is great, thanks a lot for your time.
Thanks for this! Since 2 years ago when I started working with PVE, I found LXC is good and light OS container. It likes a Swiss Army Knife .).
Super helpful tutorial!!
You may already have a follow on video or article about this, but I think it's important to create an admin account as part of this setup. One that is not root so that you can remove root from being able to login via GUI. In order to do this you'd want to create a new admin user and then add them to the sudo group. Then when that user signs into cockpit they can click this "Limited access/Admin access" toggle at the top of the page.
I more or less did the same thing. Except I used a privileged container so I could export NFS. The tricky thing with storage is user accounts. Your NAS has to have user accounts for everyone and in the case of NFS those UIDs have to match the client machine UIDs. You can share things straight off of PVE, but that would require you add all your actual users and credentials to PVE which feels wrong.
The idea I had was to put all the storage through that one NAS container and use it to share disks to the other VMs/CTs. That gets a bit broken because PVE is a bit fussy about what storage your can write what to, so you end up mapping a filesystem into the NAS container and then mounting the NFS share back on the PVE host. Which also feels wrong.
perfect amount of explanations, not to little, not too much
This is what I was looking for great tutorial thx 👍
That's super cool, thx for the video! 👍
I think it would be interesting to do similar walkthrough for NFS (next to your SMB setup) and go into details on how it should be used as shared storage for other Proxmox nodes and VMs running on external nodes (should we use VLANS to segregate node and VM traffic? Or is NFS IP based security enough? NFS version? root squash? etc)...and I was also curious about the performance of this mounted NAS/NFS running under Proxmox LXC/VM vs. Disk Passthrough to VM vs. the Native NAS/NFS performance.
NFS is a bit of a different beast to manage, since usually you'd normally use the kernel server. nfs-ganesha is a userspace nfs server which would work in a container.
For performance, Samba runs in userspace and the host ZFS pool is bind mounted into the container, so performance in an LXC will be the same as native until it hits a resource limit (either CPU or RAM). For NFS, performance using nfs-ganesha should be worse than the kernel server, however, TrueNAS uses nfs-ganesha anyway.
@@apalrdsadventures interesting stuff. I still think it would be a great video idea to complete the functionality of your awesome custom NAS.
@@apalrdsadventures ha, didn't know TrueNas always used Ganesha. I always wondered why performance was so poor...
@@apalrdsadventures Haha, yeah, I ran into that today. To do NFS, you have to make it a privileged container and enable NFS in the features ... that said, I am also running into multiple failures when trying to get it running. When doing it in an unprivileged container I get dependency errors starting the nfs-server. When I do it in a privileged container I get errors starting the cockpit service. Any thoughts?
@@drumguy1384 Did you ever get it working with NFS?
Great vid! A lot of very useful information.
Very nice tutorial well explained
Glad you like it!
Ah, great method! I've already built something up using an OpenMediaVault VM over Proxmox bc I wanted that GUI with solid user management/permissions, but I like the container/cockpit method a lot.
This is perfect for my needs, thanks for making and sharing this information mate! Now I'm motivated to build a small backup server, to make weekly backups of the proxmox 'nas' files for long-term protection. Cheers!
Glad you liked it!
I took a different approach to moving my TrueNAS data to Proxmox. I just installed Samba, NFS and WSDD on Proxmox host directly and use it's user management. Yes I still have to manage shares by via cli but I'm fine with that. Network browsing works, previous versions works (via ZFS snapshots) and even have recycle bin working via Samba.
But if you lose the host OS/hardware, then you can't "simply" restore Proxmox to a new host without manually reinstalling all the extras you have added. Putting all the extras in a LXC container means they could be easily restored from (ie;) Proxmox Backup Server.
...and if you use mountpaths in the container you can even use the zfs snapshots in SAMBA
Thanks for releasing this video! While I'm not Jellyfin'ing, the LXC tip to enable hardware Quick Sync Video worked wonders with Channels DRV on a Intel Xeon E3-1265L powered Proxmox setup. Also the Terramaster Intel NAS looks pretty sweet, keeping an eye on that one! Thanks again!
Amazing brother, thank you.
Thanks for this! Always nice to watch, very understandable and comprehensible.
Cool way. There is also a file server template in proxmox lxc templates. But with the ACL you go a step beyond
I did try the turnkey template first, but liked this solution better as something I'd run myself, with enough features in a good UI.
@@apalrdsadventures you are right about that
I am running proxmox (pimox) on an orange pi 5 with a 2TB nvme. 2 VM's, 5 LXC, it is enjoying itself at 6 Watt with some load, runs great. Cockpit looks useful, wil give it a shot. I use Alpine for the VM's and containers, it is like 30MB lol although that is quite barebone.
OpenWrt x86 is even lighter again... and has a web gui.
@@MarkConstable you’re comparing a forklift to a tugboat
Thank you so much for this!
Thank you 👍
Nice tutorial.
Thanks, this is just what I was looking for.
Enjoy!
Excellent video, thanks!
Looks great....had to adjust permissions to get it to work :)
Just as a heads up for anyone having issues running this in a privileged container you must enable nesting by adding features: nesting=1 to the container .conf before the cockpit webgui will come up.
I didn't realize Proxmox lets you add container mountpoints on its own storage pool. That opens up so many more possibilities. Now I wonder why they don't do the same for the container's root filesystem, that would make so much more sense to me.
You can add mountpoints to the host's storage as well (using pct set --mpX to create bind mounts), but in this case Proxmox's storage backend for ZFS implements container mounts as native zfs datasets. Not all backends do this, some will create separate filesystems.
@@apalrdsadventures I hadn't heard of the pct command, I assume it means Proxmox ConTainer. There's clearly much I haven't learned.
The GUI will create managed mountpoints on any storage backend that supports containers, for some (like ZFS) it uses native datasets and for others it will create a filesystem backed by a file.
From the command line you can also use pct to create mount points which refer to a path in the Proxmox host, which can include all of the file-based storage paths (like smb / nfs). pct is the command for this, and qm is for VMs.
@@apalrdsadventures Nice... the bind mounts work to export cephFS via cockpit/SMB, too (no smbmodule) ...my new erasure pool is filling up since yesterday - waiting for the 4GB RAM thin-client-2TBnvme-OSDs to OOM now ;D...PS: It's not always "dumb" to run Truenas in a VM - in my case the ZFS pool was still from the Freenas days - the host was converted from baremetalNAS with jails to pve+VM ... and it worked for years.... Thanks for the video have a great weekend!
@@apalrdsadventures
If I create a mount point within the gui (example 100GB) the mount point will be generated (new folder) on my storage, and it is included within my backup. But if I add an existing folder (which can use all of my hdd space) with all my data as mount point. This mount point is not included within the backup. Is there an work around to add existing folders or even new folders (without setting a size) wich will be included within the backup?
You sir, are a super star!
This is great stuff. I'd like to know how you maintain ZFS, as I am a complete noob with that. Maybe a future video?
I'm slowly getting there, I started with just the features that Proxmox exposes through the GUI, now there's a little bit of manual dataset creation, but zpool management is another thing
WHAT HAVE YOU DONE? Now i must tear up my system and replace my truenas in proxmox with this solution. Do you know how much work you have caused me !?!?!?! But jokes aside, great vid
Thanks! Good luck with your new system :)
Proxmox VE Helper-Scripts by tteck has added a script for installing Cockpit LXC with optional installs for file sharing plugins
Ok, this ended up being a nightmare for me to setup (likely due to a vast amount of inexperience)
Here are some of the modifications I had to do to get everything working:
1. Use the Debian 12 template instead of 11.
2. Do NOT modify the sources.list, because Debian 12 already has access to the new Cockpit
3. Instead of giving access to the entire mounted drive, make a subfolder, and give access to that instead.
4. Grant access to the group using chown -R :my-group-name /my/file/directory
5. Grant access to the user using: chown -R my-user /my/file/directory
Is this reasonable/correct? I have no clue, but it worked for me. Idk if using chown is a bad security practice or not.
Other notes:
If you do not have a disallowed-users file, it is because you are using an older version of cockpit. You either are not on Debian 12 or did not install from the backports repo (if on Deb 11)
Yes, that sounds entirely correct. chown is a much better security practice than chmod 777, which is usually what people end up doing.
Thanks for a really comprehensive tutorial.
Can't wait to implement this with Jellyfin
You're very welcome!
Excellent video!! There is also an option with Turnkey that has Samba pre-installed and pre-configured. Have you tried that? and what are the disadvantages compared with the Cockpit approach?
I tried Turnkey fileserver first, found that the GUI wasn't as good as Cockpit, the Webmin-based manager has a ton of options to manage services on the system that shouldn't be managed in an appliance (like Apache settings, or hostname / network which are managed by Proxmox), and it doesn't natively support IPv6. Cockpit is also lighter weight than running Apache and runs itself as the logged in user.
@@apalrdsadventures and your solution can even work on pimox and a small raspberry.
I'd love a Proxmox tutorial on using LVM to have a pool of disks I can add to & remove from which can be mounted as a single logical volume on /mnt/storage then passed through/shared by multiple containers (TurnKey SMB or Cockpit, Deluge, Plex, etc).
My use case is setting up a non-critical home NAS with a bunch of drives I have lying around. I can't use zfs raid due to the varying disk types/sizes and the desire to add/remove drives over time (I think zfs raid5/6 will limit the size to the smallest drive in the array and you're limited to 5 drives?).
I'm thinking that the flexibility of LVM means that I could set alerts on SMART warnings and simply remove/replace a disk if it looks unhealthy somewhat mitigating the need for redundancy - but worst case scenario I _think_ LVM doesn't drop the whole disk array if a single physical disk dies, only the data on that drive meaning I can pair a 1TB SSD next to an 8TB HDD without worrying too much that the 8tb would get dropped if the SSD fails.
So far I've tried creating a logical lvm volume from a pool of disks however mounting them makes them show up as 100% used in Proxmox (though I don't know what that actually means).
Haha, maybe I should have bought an off the shelf NAS rather than try to DIY it. halp pls
Excellent video as always, could you please create a video with iVentoy using a NAS for ISO storage on Proxmox
Does anyone else have relatively high CPU usage for cockpit processes when setting up this way? Was consuming around 20-25% CPU on my Terremaster/Proxmox, even with nothing going on. I ended up stopping the cockpit service and just running plain old samba by itself.
I also had to set this up as a privileged container so it had read/write access to the shares. This also required bind mounts of the ZFS datastores from the Proxmox host to the container. Nothing I could do would allow even local users to write to the mounts local to the containers or the shares.
But all is running now and I like this a lot better than my prior attempt at passthru to TrueNAS in a VM. Thanks apalrd for the idea!
I'm not sure why Cockpit is using so much, it shouldn't have any long-running processes since it uses systemd socket activation.
As to permissions, unprivileged containers have an offset user id / group id in the host (root in the container is uid/gid 100000 on the host) so bind mounting from host to container you'll need to either chown to the guest's uid or gid, or chmod in a way that the guest has access. Privileged containers don't have the uid/gid offset.
same packages installed like in video. 0% if cockpit is not open in browser, 0-4% if open while running it on atom cpu. 60mb ram usage.
Had the same issue, but closing the cockpit tab in my browser fixed it for me.
Followed guide, everything was working great except transferring large files (14GB and larger), one or two large files might copy but the container would always lock up or samba within the container would crash. Increasing the memory from 1/2 GB to 8 GB fixed all issues. FYI this is on a 10gb (RJ45) network
Great one 👌, please make a video for odk Central installation on ubuntu local machine, thanks 🙏.
I have an issue with logging in. I can log into the proxmox lxc debian console, but I can't log into the web ui. I can still access all the shares I setup through cockpit though.
I have followed along with this guide and your jellyfin guide. My fileserver is "unprivledges" while the jellyfin is priveledged container. I used the manual steps to add mount points to both. The problem is on the unprivledged container the ownership of the mount is nobody and nogroup because the root has a differnent UID I think. And I can't change the permissions on the fileserver
When I make both containers priviledged the ownership of mount point works. Other option is to just put both services in 1 container.
I have a weird issue. Cockpit keeps using up about 20% of my available CPU power after following this guide. Cockpit is obviously trying to do something I just have no idea what. I've taken to manually turning cockpit on/off using systemctl whenever I need to log in but I'm hoping to find a solution to this problem...
Apalrd, this is a great guide and series. Thanks for putting it together it has helped me quite a bit!
great video dude! thanks
I flailed around in Proxmox for a day before installing TrueNAS, shouldve watched this video. Definitely agree that the "just run TrueNAS with passthrough" advice seems really unsatisfying.
There should be a way to map it to a Windows machine from outside the network. That way, if you're on vacation or something, you can access files or perhaps offload pictures from say your phone to a laptop that has the mapped "drive".
Get a VPN into your house. Wire guard or tailscale ECT. Then just connect like you are on your home network.
I have a running setup thanks to you're video. Now I would like to implement syncthing in this. But I can't yet seem to get this to work like I think it should. Backup/Sync from cockpit shares to backup NAS share. Do you have any experience with this? Or maybe this is an Idea for a next video?
I was always wondering why everybody is installing TrueNAS on Proxmox for filesharing and ZFS when proxmox has the same funcionality. There is no need to passthrough Sata controlers, PCI-e and waste resources for another OS which can do the same thing what proxmox can do... TrueNAS is great (except that it doesnt allow to use SDD which its installed for anything and literally wasting SSD).
In proxmox there is turnkey fileserver LXC template which automatically makes filesharing works on proxmox.
I did try the turnkey LXC before setting this up and was not happy with it compared to Cockpit. I found the UI to be worse than Cockpit, Webmin includes management of a lot of things that shouldn't be touched (such as apache2 which runs the turnkey GUI, and hostname / networking settings which Proxmox overwrites), cockpit runs as the logged in user and inherits their permissions from the Linux system instead of doing its own user management and security, and Turnkey didn't deal with IPv6 properly out of the box.
So pleased to have found your channel. Is there an LXC container manger (like exists within Proxmox) for Cockpit or some other? I see it can do VMs and I'm already familiar with Virt-manager. I'd like to just run Debian with a gui desktop, kvm-qemu, LXC containers and Docker within one of those too but also be able to access and work at the machine itself. I see Incus is coming with Trixie. Not sure about LXD now that it's getting dropped after bookworm?
Nice! proxmox ui seems like the best.
without an add on card I don’t have the ability to pass thru my hdd to truenas vm.
now to set up hand break and makemkv containers and have them have access to those storages.
You really don't need an add on card, you can pass storage from Proxmox into containers with a bind mount.
@@apalrdsadventures you do for Truenas to give direct disc access, but your method that I'm trying now will omit truenas. Just wondering if I'll miss any better zfs perks of truenas?
Thank for the video, this convinced me to migrate from virtualized truenas to this way, BUT can you explain the drop of perfomance? truenas used to be much faster
What performance difference are you seeing? TrueNAS (SCALE) should have very similar zfs tuning to Proxmox VE, but if you are coming from CORE you will have less ARC space.
Great content man!
What a lunatic idea, I like it 😂
Cool nice video. I use Proxmox running quite a few debian vm's. Nice addition. Sub'd and liked!