anchor.diff:  ----
   ====
   
  -To create the logging pod, create a file with the following contents in the
  -directory specified by `*podManifestConfig.path*` above:
  -
  -====
  -
  +[NOTE]
  +====
  +If you are running OpenShift as an all-in-one with `openshift start` (either directly or via a systemd unit), node configuration
  +is overwritten at each restart. You will need to use `openshift start --write-config=<path-to-config-dir> <parameters>` in order
  +to write the master and node configuration, then modify your server command line to look like:
  +
  +    openshift start --master-config=/<config-dir>/master/master-config.yaml \
  +                    --node-config=/<config-dir>/<node-dir>/node-config.yaml
  +====
  +
  +To create the logging pod, create a file with the following contents in
  +the directory specified by `*podManifestConfig.path*` above (if relative
  +as defined above, then it is relative to the node config dir):
  +
  +====
   [source,yaml]
   ----
   apiVersion: v1
  
positive.code:     - name: varlibdockercontainers
        mountPath: /var/lib/docker/containers
        readOnly: true
    volumes:
    - name: varlog
      hostPath:
  
negative.code: This starts a pod on the node and posts the container logs to *Elasticsearch*.
  
  To validate it is working, you can query *Elasticsearch* and check that the data
  is correctly being persisted. First, identify the *Elasticsearch* service:
  
  ----
  $ oc get service -l component=elasticsearch
  ----
  
  Then query *Elasticsearch*, replacing the pod ID with one returned from the
  above command for `es-logging`:
  
  ----
  $ curl -s <service_ip>:9200/_cat/indices?v
  ----
  
  You should see output similar to the following:
  