The technique I’m using above uses devicemapper as the storage driver and the docker images seem to be placed in a 100G sparse file “data”. /mnt/docker/devicemapper/devicemapper/data
Is there a way to use NFS and have the images be separate files (for backup etc.) or subvolumes such as when using btrfs as the storage driver?
@ Akshay, I have a test environment so I have a wildcard export with no_root_squash. I’m using freenas, but on linux nfs server /etc/exports would be something like :
/path/to/exported/directory *(rw,no_root_squash)
As long as your host can write a file into the NFS share then docker should work well. Test writing a file into the NFS mount to check if you have permissions.
Interested to here if others are using docker over NFS both for mount NFS share to containers and as a shared persistent storage for the images. Especially interested if 1.7 made improvements for this.
Hi;
I’m running Docker on CoreOS and for reliability using a NFS built on Debian 7.
My NFSServer Options are: rw,sync,fsid=0,crossmnt,no_subtree_check,no_root_squash.
For explaination of each : http://linux.die.net/man/5/exports
Hey everyone. Not quite the same thing, but I wrote up a blog post about how we use NFS with docker volumes in Docker Trusted Registry. You can read about it here.