-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
30.0.1.Final
-
None
-
-
---
-
---
Hello,
I'm using Wildfly 30.0.1 Bootable. I've built a JIB image of it and trying to start it in debug mode, such that I could debug a JAR deployed inside. I'm using `jib-maven-plugin`, with maven 3.9.6, with the below configuration:
<plugin>
<groupId>com.google.cloud.tools</groupId>
<artifactId>jib-maven-plugin</artifactId>
<configuration>
<containerizingMode>packaged</containerizingMode>
<to>
<image>wildfly-bootable/server-layer</image>
</to>
<container>
<mainClass>org.wildfly.core.jar.boot.Main</mainClass>
<args>
<arg>-b=0.0.0.0</arg>
<arg>--deployment=/deployments/ROOT.war/</arg>
<arg>--debug=*:8787</arg>
</args>
<ports>
<port>8080</port>
<port>8787</port>
</ports>
</container>
</configuration>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>dockerBuild</goal>
</goals>
</execution>
</executions>
</plugin>
After creating the image `wildfly-remote/server-layer` I'm using the same plugin to extend it and create another image, named `wildfly-remote/app-layer`, as a layer of the first one. Now when I'm running this image, for example:
docker run -p 8080:8080 -p 8787:8787 wildfly-bootable/app-layer:latest
I'm getting the error message below:
java.lang.RuntimeException: WFLYJAR0011: Unknown argument --debug=*:8787
However, as far as I've seen in the doc, this is how the debug mode should be activated when running Wildfly in a Docker container.
What am I doing wrong here ?
