Bjoern Stuetz created WFLY-8133: ----------------------------------- Summary: Mount point not found exception raised by createTempFileWithAttributes on overlayfs [JDK-8165852] Key: WFLY-8133 URL: https://issues.jboss.org/browse/WFLY-8133 Project: WildFly Issue Type: Bug Components: CLI Environment: WildFly on Docker with overlayfs or overlayfs2 as storage driver # docker info | grep -i storage aufs: works (e.g., boot2docker, legacy minikube) overlay (e.g., CoreOS, current minikube): problem devicemapper (e.g., CentOS): works overlay2 (e.g., Docker for Mac): problem Reporter: Bjoern Stuetz Assignee: Jason Greene Mount point not found exception raised by createTempFileWithAttributes on overlayfs [JDK-8165852], i.e., /opt/jboss/bin/jboss-cli.sh --file=/opt/jboss/jboss-config.cli inside a Docker container running on overlayfs as storage driver causes: {code:java} java.io.IOException: Mount point not foundImage at sun.nio.fs.LinuxFileStore.findMountEntry(LinuxFileStore.java:91) at org.jboss.as.controller.persistence.FilePersistenceUtils.createTempFileWithAttributes(FilePersistenceUtils.java:117) at org.jboss.as.controller.persistence.FilePersistenceUtils.writeToTempFile(FilePersistenceUtils.java:104) {code} due to OpenJDK bug/overlayfs bug. We acknowledge that this is in fact an OpenJDK AND/OR overlayfs bug. However everything seems to run fine in WildFly except once the backup of the config is triggered, for example by using the cli. Hence WildFly is of limited functionality when the more and more popular overlayfs storage driver is used, and the WildFly team might be interested in providing a workaround on their side since there is no indication the OpenJDK bug will be promptly fixed. We are happy to help in any way, we are still trying to find a workaround on Java or WildFly side; but might need insights on why findMountEntry is invoked. Java Bug Overview: https://bugs.openjdk.java.net/browse/JDK-8165852 http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u... Wildfly Stack Overflow issue, not solved: https://stackoverflow.com/questions/41022393/mount-point-not-found Background Info: http://mail.openjdk.java.net/pipermail/nio-dev/2016-October/003915.html A) chroot environment [1] B) Docker container with overlay and overlay2 storage drivers [2] C) btrfs file system with an unmounted sub-volume [2] [1] https://bugs.openjdk.java.net/browse/JDK-8165323 - cannot get FileStore in chroot environment [2] https://bugs.openjdk.java.net/browse/JDK-8165852 - cannot get FileStore for a file in overlayfs in Docker Docker file system/storage driver: https://docs.docker.com/engine/userguide/storagedriver/selectadriver/) Yum yum-plugin-ovl, similar problem: https://github.com/CentOS/sig-cloud-instance-images/issues/15 -- This message was sent by Atlassian JIRA (v7.2.3#72005)