What a journey it has been trying to get my NAS to mount in these LXCs in Proxmox. I’ve tried quite a bit of variations in the MOUNT command and ultimately landed on:
sudo mount -t nfs 192.168.1.18:/volume1/Video /media/synologydf -h
I settled on this simple approach after trying to authenticate SMB and later NFS with a username/password approach for about a week. Most of that struggle was due to unprivileged LXCs in Proxmox sharing so many resources with the host node (as previously discovered with kernel configs). Further that confusion by adding on another layer of permissions with containers running via Docker Engine and Portainer. (A lot of fun happened this week with containers, lol)
A Reddit post tipped me off this simpler approach:
I had to configure, guest access to the specific folder on the NAS the containers need access to, then mount it. Which the above command does, but not automatically on boot.
/etc/fstab
In order to mount the remote directory on startup we must modify /etc/fstab. Then it will automatically start after any restarts or power outages. Seems simple enough, now I just got to translate the above command correctly for fstab. A cleaner graphic is provided by Linuxize if the Wikipedia example seems overwhelming.
That was not enough for me however. I had to see why there is an unusual amount of white space between each category. Seems based on the conversations at Stackexchange it’s mostly for appearances and readability.
So the end result was formatted:
You see the lack of consistency in white space – if you appreciate organization and structure that could definitely bothersome. Now for a quick restart to test.
sudo reboot now
Checking Sonarr reveals in fact the containers are still seeing the NFS volume mount after restart. This is great news! If only you seen the offline struggles to get to this moment! So why did I go through all the effort this week you may ask?
Sonarr, Radarr, Jackett, qBitorrent in Windows Server 2025
I can see the appeal of why so many companies would rather pay the license fee for Microsoft Windows. The effort it took me to configure services in Windows was effortless by comparison to Linux. Many people fault Linux for it’s difficulties, but often take for granted how many hours of their lives they have spent training in a Windows environment. Of course it’s easier! You’ve practiced!
As you can see here Windows Server loves RAM:
This coupled with a desire to maintain mobility across the cluster has been the motivation for configuring containers in their own separate LXCs. But after getting frustrated trying to pass permissions for NFS mounts through to Docker and Portainer I settled for putting media containers into a single Ubuntu Server install. I don’t want to configure 5-8 LXCs…. yet!
Back to Windows Server! As you can see below the visual comfort of this three step process will have you installed and accessible across the LAN quickly. Run your desired .exe:
Configure your firewall to allow access outside the server (select Allow another app.. if necessary):
For the Windows Server I utilized the Samba protocol / SMB / CIFS. The folder directory I got from my SMB settings in the Synology NAS under File Services > SMB.
And after that can go through and configure all your Sonarr/Radarr directories and get lost in their respective configuration documentation, haha! But you can see visually things are simpler here. You don’t have to struggle through finding the unknown usage of a command modifier – or getting lost on permission related issues for days.
Leave a Reply