CentOS-7 reports syntax errors on startup

[jdeathe]

mv: cannot move `/etc/services-config/httpd/conf.d/10-ssl-vhost.conf' to a subdirectory of itself, `/etc/services-config/httpd/conf.d/10-ssl-vhost.conf.off'

The bootstrap script fails on the move command used to disable the the SSL VirtualHost configuration when not required.

[jdeathe]

The CentOS-7 docker host used for testing is using overlay file system which has known issues with this - need to rebuild my test VM using an alternative file system. Will likely need to change the CentOS Atomic Host test VM too.

• os.rename throws exception when renaming directories on lower overlayfs layers moby/moby#25409
• Same image & container has different behavior on different hosts moby/moby#26317

[jdeathe]

Not reproducible with CoreOS host which uses overlay too.

[jdeathe]

• https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/7/paged/getting-started-with-containers/chapter-7-managing-storage-with-docker-formatted-containers
• https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.2_Release_Notes/technology-preview-file_systems.html

[jdeathe]

Full support is available for OverlayFS when used with Docker under the following restrictions:

• OverlayFS is only supported for use as a Docker graph driver. Its use can only be supported for container COW content, not for persistent storage. Any persistent storage must be placed on non-OverlayFS volumes to be supported. Only default Docker configuration can be used; that is, one level of overlay, one lowerdir, and both lower and upper levels are on the same file system.
• Only XFS is currently supported for use as a lower layer file system.
• SELinux must be enabled and in enforcing mode on the physical machine, but must be disabled in the container when performing container separation; that is, /etc/sysconfig/docker must not contain --selinux-enabled. SELinux support for OverlayFS is being worked on upstream, and is expected in a future release.
• The OverlayFS kernel ABI and userspace behavior are not considered stable, and may see changes in future updates.
• In order to make the yum and rpm utilities work properly inside the container, the user should be using the yum-plugin-ovl packages.
  Note that OverlayFS provides a restricted set of the POSIX standards. Test your application thoroughly before deploying it with OverlayFS.
  Note that XFS file systems must be created with the -n ftype=1 option enabled for use as an overlay. With the rootfs and any file systems created during system installation, set the --mkfsoptions=-n ftype=1 parameters in the Anaconda kickstart. When creating a new file system after the installation, run the # mkfs -t xfs -n ftype=1 /PATH/TO/DEVICE command. To determine whether an existing file system is eligible for use as an overlay, run the # xfs_info /PATH/TO/DEVICE | grep ftype command to see if the ftype=1 option is enabled.
  There are also several known issues associated with OverlayFS as of Red Hat Enterprise Linux 7.2 release. For details, see 'Non-standard behavior' in the Documentation/filesystems/overlayfs.txt file.

[jdeathe]

My CentOS-7 VM image uses ext4 instead of the standard xfs file system. This was done to be consistent with the CentOS-6 VM but should test changing to a build that uses xfs instead.

• https://github.com/jdeathe/packer-centos-7/blob/develop/CentOS-7-Minimal-virtualbox.json#L17

SELinux is set to permissive on my Vagrant box too so need to test changing that on the docker host too.

[jdeathe]

Not reproducible when using CentOS-7 official Vagrant Image: https://seven.centos.org/2016/10/updated-centos-vagrant-images-available-v1609-01/

They have moved to using XFS file system too so this issue is looking more likely with my custom Vagrant build than with the container image.

[jdeathe]

Using the CentOS-7 official Vagrant Image I run into a different issue with the httpd24u + php56u based tag where the configuration files do not get loaded resulting in an access denied to "/" message. The image tags based on the standard packages works without issues however.

[jdeathe]

I've already solved this issue before! I am going to revert back to my own CentOS-7 Vagrant image and replace the mv operation with cat which will work without issues.