Hey.

I'm trying to run docker container with custom config:

<?xml version="1.0" encoding="UTF-8"?>
<infinispan
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="urn:infinispan:config:9.4 http://www.infinispan.org/schemas/infinispan-config-9.4.xsd"
        xmlns="urn:infinispan:config:9.4">
      <cache-container default-cache="default">
          <transport cluster="testCluster"/>          
          <replicated-cache name="repl-sync" mode="SYNC">
            <expiration lifespan="5000"/>
          </replicated-cache>
      </cache-container>
</infinispan>

This file validates against .xsd

Executing

sudo docker run -v /home/[user]/docker/:/opt/jboss/infinispan-server/standalone/configuration/extra/ jboss/infinispan-server:9.4.11.Final -c /extra/customConfig.xml

and getting error:

16:26:06,961 INFO  [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final

16:26:07,615 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.3.Final

16:26:07,626 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final

16:26:07,800 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: Infinispan Server 9.4.11.Final (WildFly Core 6.0.2.Final) starting

16:26:08,679 ERROR [org.jboss.as.controller] (Controller Boot Thread)

 

OPVDX001: Validation error in customConfig.xml ---------------------------------

|

|  1: <?xml version="1.0" encoding="UTF-8"?>

|  2: <infinispan

|     ^^^^ Unexpected element '{urn:infinispan:config:9.4}infinispan'

|

|  3:         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

|  4:         xsi:schemaLocation="urn:infinispan:config:9.4 http://www.infinispan.org/schemas/infinispan-config-9.4.xsd"

|  5:         xmlns="urn:infinispan:config:9.4">

|

| The primary underlying error message was:

| > ParseError at [row,col]:[2,1]

| > Message: Unexpected element '{urn:infinispan:config:9.4}infinispan'

 

Interesting thing is that I get same error with simplest config like: "<infinispan/>", so I assume it's not the problem of config file.

Searching for this error message led me to some problems with jar hell. But I have no Idea if it's the case or how to dig into docker container to find it out.

Thanks for your time!