anchor.diff:  *fsGroup* security context setting but the idea for allowing
   write permissions is the same.
   
  -Here are the instructions I use when setting up NFS:
  +You will then need to modify the /etc/exports file. 
  +....
  +sudo vi /etc/exports
  +....
  +
  +The /etc/exports file should contain a line similar to this one except with the applicable IP address specified:
  +....
  +/nfsfileshare 192.168.122.9(rw,sync)
  +....
  +
  +After saving and closing the file, you will need to re-export all directories:
  +....
  +sudo exportfs -r
  +....
  +
  +Detailed instructions that you can use for setting up a NFS server on Centos 7 are provided in the following link.
   
   http://www.itzgeek.com/how-tos/linux/centos-how-tos/how-to-setup-nfs-server-on-centos-7-rhel-7-fedora-22.html
   
  
positive.code: The examples specify a test NFS server running at IP address 192.168.0.103.
  
  On that server, the /etc/exports file looks like this:
  
  ....
  /nfsfileshare *(rw,sync)
  ....
  
negative.code: 
  The permissions on the NFS path are set as follows:
  ....
  sudo mkdir /nfsfileshare
  sudo chmod 777 /nfsfileshare
  ....
  
  Most of the Crunchy containers run as the postgres UID (26), but you
  