Open ErSauravAdhikari opened 21 hours ago
I'm always frustrated that there is no easy way to configure external volume mounts based on network attached storage.
Allow the admin to configure the following features
User permission can also be tied to the said volume destination (Linked to issue: #788 )
The volume destination can be something like the following:
For remote we have options such as: nfs, glusterfs, iscsi, sshfs, cifs, etc.
Creating docker volume manually and linking them
For example:
docker volume create --driver local \ --opt type=nfs \ --opt o=addr=[ip-address],rw \ --opt device=:[path-to-directory] \ [volume-name]
Docker run command referenced from: https://phoenixnap.com/kb/nfs-docker-volumes
Maybe (Need help)
It would be very nice to have
What problem will this feature address?
I'm always frustrated that there is no easy way to configure external volume mounts based on network attached storage.
Describe the solution you'd like
Allow the admin to configure the following features
User permission can also be tied to the said volume destination (Linked to issue: #788 )
The volume destination can be something like the following:
For remote we have options such as: nfs, glusterfs, iscsi, sshfs, cifs, etc.
Describe alternatives you've considered
Creating docker volume manually and linking them
For example:
Additional context
Docker run command referenced from: https://phoenixnap.com/kb/nfs-docker-volumes
Will you send a PR to implement it?
Maybe (Need help)