Jens Nehlmeier

Really nothing special. I use docker on macOS 10.15.7 and simply did your short tutorial without modifying any dockerfile build arg. Then I executed `docker run -p 80:80 -p 443:443...

Ok I have to correct me. I already had something running on port 80 and 443 and thus used different ports. And that seems to be the issue. 1. Add...

@joakime Not sure if you want to have an extra issue for this opened by I am currently trying to migrate to the official jetty image and while everything seems...

Hm I can't even workaround it by creating an my-app.mod file instead with an `[exec]` block as above and adding that module to jetty. Basically I can not do -...

Ok did a little debug and here is what happens ```dockerfile FROM jetty:10.0.15-jdk17-eclipse-temurin ENV JAVA_OPTIONS --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED \ --add-opens java.base/sun.nio.ch=ALL-UNNAMED \ --add-opens java.base/jdk.internal.misc=ALL-UNNAMED \ --add-opens java.base/java.nio=ALL-UNNAMED \ -Dio.grpc.netty.shaded.io.netty.tryReflectionSetAccessible=true ``` generates...

@joakime I am not sure how/if it will affect the web application running in jetty. So I tried to avoid using JPMS mode of jetty. Especially because I have a...

Well shouldn't this be `JAVA_OPTIONS`? But as shown above it does not work at all for these kind of parameters.

@joakime So I guess two things need to be done: 1. Handle the contents of `JAVA_OPTIONS` better because currently `JPMS` parameters are somehow processed but swallowed so that the final...

Ok I tried `[jpms]` now but then the container fails to start because `generate-jetty-start.sh` does an `egrep '[^ ]*java .* org\.eclipse\.jetty\.xml\.XmlConfiguration '` on the dry-run result which results in an...

> We're of course considering what to do to avoid the warning in the future @dadza Has any progress been made on this issue? With JDK 17 LTS being out...