Open nicolasduminil opened 5 months ago
Hi, It would really help to have a reproducer for your issue (having a simplified github project that highlights the problem). I suspect that you could reproduce the problem on bare-metal, jib docker image shouldn't be bound to the problem. Thank-you.
Hello,
I'm using
wildfly-jar-maven-plugin:10.0.0.Final
to provision a wildfly bootable 30.0.1.Final. Here is the config:This is a hollow JAR. Then, I create a JIB base image and I extend it to add an application deployed as ROOT.war. Running the final image with Docker raises the following exception:
However, looking in the hollow JAR
MANIFEST.MF
file I can see:Isn't it supposed to avoid this exception ? Does the fact of extending the associated image have an impact in this case ? The final image is built with the JIB plugin, as follows:
The
MANIFEST.MF
file of the associated WAR doesn't contain the requiredAdd-Exports
andAdd-Open
as does the hollow JAR. Is that normal ?In any case, what am I supposed to do in order to avoid this exception ?
Many thanks in advance.
Kind regards, Nicolas