- 162
- 45
- NAS
- DS918+ (8GB RAM, 4x WD RED 4TB SHR) ; EATON Ellipse PRO 1200FR
- Operating system
- Windows
- Mobile operating system
- Android
Hello all,
After having issues with Docker NginxPM not able to get the real client IP and wanting to use something more "standard" than MacVLAN, I decided to pull the trigger and create a Debian10 VM on my Synology to host a few containers such as AdGuardHome, NginxPM and have their config files and data hosted on a NFS share.
The VM is now up and running with docker, docker compose, portainer agent (so it can be managed from the portainer hosted directly on the NASes docker) and nfs-common but I did not manage to get the NFS share to work properly.
I needed to do something as simple to maintain as possible and also easy to rebuild in case of issue.
At some point, I managed to get one NFS share visible and usable on the VM but unfortunately, the containers were not able to use the share so until I get it working properly, I manually sync one of the VMs local folder containing the containers data (mounted volumes) with the NFS share mounted on the VM.
I did one attempt today to create a new share on the NAS and try to get it mounted on the VM but it seems like I something I did is not right but I can't figure out what ...
Below how my Share is configured (sorry interface is in french :P ) :
- Permissions (user has on Syno has the same ID as the user in VM)
- File Station
- NFS
And what I did in the VM to mount the share (it failed)
It would be great if anyone could help me go through this configuration.
Thanks.
After having issues with Docker NginxPM not able to get the real client IP and wanting to use something more "standard" than MacVLAN, I decided to pull the trigger and create a Debian10 VM on my Synology to host a few containers such as AdGuardHome, NginxPM and have their config files and data hosted on a NFS share.
The VM is now up and running with docker, docker compose, portainer agent (so it can be managed from the portainer hosted directly on the NASes docker) and nfs-common but I did not manage to get the NFS share to work properly.
I needed to do something as simple to maintain as possible and also easy to rebuild in case of issue.
At some point, I managed to get one NFS share visible and usable on the VM but unfortunately, the containers were not able to use the share so until I get it working properly, I manually sync one of the VMs local folder containing the containers data (mounted volumes) with the NFS share mounted on the VM.
I did one attempt today to create a new share on the NAS and try to get it mounted on the VM but it seems like I something I did is not right but I can't figure out what ...
Below how my Share is configured (sorry interface is in french :P ) :
- Permissions (user has on Syno has the same ID as the user in VM)
- File Station
- NFS
And what I did in the VM to mount the share (it failed)
root@deb10vm:/# mkdir /mnt/docker-nfs
root@deb10vm:/# mount 192.168.1.250:/volume3/NFS_VM_Share /mnt/docker-nfs
mount.nfs: access denied by server while mounting 192.168.1.250:/volume3/NFS_VM_Share
It would be great if anyone could help me go through this configuration.
Thanks.