Need to investigate why these errors are occurring. They seem to be related to different logging files across different containers. The errors eventually go away, but logging errors (that are then resolved automatically) is giving the impression of an unstable OOM environment, and needs to be resolved.

Example errors:

nux.go:247: starting container process caused \\\"process_linux.go:359: container init caused \\\\\\\"rootfs_linux.go:53: mounting \\\\\\\\\\\\\\\"/dockerdata-nfs/onap/log/mso/logback.workflow-message-adapter.xml\\\\\\\\\\\\\\\" to rootfs \\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/e5c47f57892fc1cfb4c789d7b2900f64a220e69e4d0186ff5de8189782d66b14\\\\\\\\\\\\\\\" at \\\\\\\\\\\\\\\"/var/lib/docker/aufs/mnt/e5c47f57892fc1cfb4c789d7b2900f64a220e69e4d0186ff5de8189782d66b14/var/berks-cookbooks/mso-config/files/default/mso-workflow-message-adapter-config/logback.workflow-message-adapter.xml\\\\\\\\\\\\\\\" caused \\\\\\\\\\\\\\\"not a directory\\\\\\\\\\\\\\\"\\\\\\\"\\\"\\n\""}