anchor.diff:    4m		4m		1	{kubelet ose70.rh7}	spec.containers{busybox-nfs-pod}	Created		Created with docker id 346d432e5a48
     4m		4m		1	{kubelet ose70.rh7}	spec.containers{busybox-nfs-pod}	Started		Started with docker id 346d432e5a48
   ----
  -As you can see, both containers are using the same storage claim that is attached to the same NFS mount on the back end.
  +====
  +
  +As you can see, both containers are using the same storage claim that is
  +attached to the same NFS mount on the back end.
  
positive.code: By default, SELinux does not allow writing from a pod to a remote NFS server. To
  enable writing to NFS volumes with SELinux enforcing on each node, run:
  
  ----
  # setsebool -P virt_sandbox_use_nfs on
  # setsebool -P virt_use_nfs on
  ----
  
  [NOTE]
  ====
  The `virt_sandbox_use_nfs` boolean is defined by the *docker-selinux* package.
  If you get an error saying it is not defined, please ensure that this package is installed.
  ====
  
  == Creating the Pod
  A pod definition file or a template file can be used to define a pod. Below is a
  pod specification that creates a single container and mounts the NFS volume for
  
negative.code: ----
  # oc create -f nfs.yaml
  pod "nginx-nfs-pod" created
  ----
  ====
  
  Verify that the pod was created:
  
  ====
  ----
  # oc get pods
  NAME                READY     STATUS    RESTARTS   AGE
  nginx-nfs-pod       1/1       Running   0          4s
  