Mount point not found

Question

I am running a Java EE 7 application (with a lot of classes) on WildFly with Jackson, CDI, Swagger and Drools. I think that this error originated when I started using Drools, however I am not certain. As there is no reference to a local class, I have no idea where the error originated.

AFAIK, the application works without problems, but when I deploy the application, I get the following error:

ERROR java.io.IOException: Mount point not found
ERROR   at sun.nio.fs.LinuxFileStore.findMountEntry(LinuxFileStore.java:91)
ERROR   at sun.nio.fs.UnixFileStore.<init>(UnixFileStore.java:65)
ERROR   at sun.nio.fs.LinuxFileStore.<init>(LinuxFileStore.java:44)
ERROR   at sun.nio.fs.LinuxFileSystemProvider.getFileStore(LinuxFileSystemProvider.java:51)
ERROR   at sun.nio.fs.LinuxFileSystemProvider.getFileStore(LinuxFileSystemProvider.java:39)
ERROR   at sun.nio.fs.UnixFileSystemProvider.getFileStore(UnixFileSystemProvider.java:368)
ERROR   at java.nio.file.Files.getFileStore(Files.java:1461)
ERROR   at org.jboss.as.controller.persistence.FilePersistenceUtils.getPosixAttributes(FilePersistenceUtils.java:124)
ERROR   at org.jboss.as.controller.persistence.FilePersistenceUtils.createTempFileWithAttributes(FilePersistenceUtils.java:112)
ERROR   at org.jboss.as.controller.persistence.FilePersistenceUtils.writeToTempFile(FilePersistenceUtils.java:99)
ERROR   at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.doCommit(ConfigurationFilePersistenceResource.java:55)
ERROR   at org.jboss.as.controller.persistence.AbstractFilePersistenceResource.commit(AbstractFilePersistenceResource.java:58)
ERROR   at org.jboss.as.controller.ModelControllerImpl$4.commit(ModelControllerImpl.java:789)
ERROR   at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:743)
ERROR   at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:680)
ERROR   at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
ERROR   at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329)
ERROR   at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:400)
ERROR   at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:222)
ERROR   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208)
ERROR   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)
ERROR   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152)
ERROR   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148)
ERROR   at java.security.AccessController.doPrivileged(Native Method)
ERROR   at javax.security.auth.Subject.doAs(Subject.java:422)
ERROR   at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
ERROR   at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148)
ERROR   at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
ERROR   at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)
ERROR   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
ERROR   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
ERROR   at java.lang.Thread.run(Thread.java:745)
ERROR   at org.jboss.threads.JBossThread.run(JBossThread.java:320)

I am using Docker Desktop for Windows. Can anyone help me out where to look for a solution, where this error is coming from?

Answer 1

I had this error in the last days using the elasticsearch docker image in Docker for Mac. I have fixed the issue change the storage driver from overlay2 to aufs (not sure yet about the real impact of this change). You can change the store driver:

• Docker preferences
• Daemon tab
• Advanced tab

• Edit the json like this:

  { "storage-driver" : "aufs" }

I hope it helps you

Answer 2

We ran into the same issue, when running a custom elasticsearch container on OS X. The container was built on docker.elastic.co/elasticsearch/elasticsearch:5.3.0. However, the container started up cleanly on a similar environment, which seemed suspicious.

The problem was finally resolved, when we noticed that docker info showed different storage drivers for us. AUFS seems to work, where as overlay2 does not. It can be changed, but you will have to refetch and rebuild your current containers.