This prevents the server from starting with overlayfs since rename isn't supported unless both source and destination are in the top layer.

Renaming directories: Calling rename(2) for a directory is allowed only when both the source and the destination path are on the top layer. Otherwise, it returns EXDEV error (“cross-device link not permitted”). Your application needs to be designed to handle EXDEV and fall back to a “copy and unlink” strategy.

See: https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/

Kudos to Jan-Otto Kröpke for discovering the underlying cause.

The error is

ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: java.lang.IllegalStateException: WFLYCTL0056: Could not rename /opt/eap/standalone/configuration/standalone_xml_history/current to /opt/eap/standalone/configuration/standalone_xml_history/20161117-180800876