[jboss-jira] [JBoss JIRA] (WFCORE-3937) Error when running configured wildfly
[
https://issues.redhat.com/browse/WFCORE-3937?page=com.atlassian.jira.plug...
]
Yeray Borges Santana commented on WFCORE-3937:
----------------------------------------------
This is also hitting the wildfly-s2i cloud image when drivers are configured at S2I phase;
the standalone_xml_history is being created at S2I phase and it ends up in a different
overlay filesystem mounted by Docker in the final image, thanks [~jdenise] for pointing me
out to the Overlays Filesystem concept.
Files.move is unable to move directories if they are in different partitions (overlay
filesystem mounted in the docker image)
Error when running configured wildfly
-------------------------------------
Key: WFCORE-3937
URL: https://issues.redhat.com/browse/WFCORE-3937
Project: WildFly Core
Issue Type: Bug
Components: Management
Affects Versions: 5.0.0.Final
Reporter: Stephen Buergler
Assignee: Jeff Mesnil
Priority: Minor
Attachments: Dockerfile
08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could
not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to
/opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673:
java.nio.file.DirectoryNotEmptyException:
/opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current
...
08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could
not create a timestamped backup of current history dir
/opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may
still include versions from the previous boot.
To reproduce:
docker build -t testing .
docker run --rm -it testing
--
This message was sent by Atlassian Jira
(v7.13.8#713008)