Debug port not working in Docker container

[tmulle]

Describe the bug

This I think is related to #7890

When building my docker image using the Dockerfile.jvm script generated by the code.quarkus.io page and exposing port 5005 like the comments say, I'm unable to connect to the application inside Docker.

I get an error when using NetBeans Remote Debug:

Attaching to localhost:5005
handshake failed - connection prematurally closed

This is how I run my application in docker:

docker run -i --rm -p 5005:5005 -p 8080:8080 -e JAVA_DEBUG=true ....the rest of the line

and this is the log file INSIDE the container. Notice the agent command doesn't have *:5005 or even 0.0.0.0:5005 like the ticket says it should.

Starting the Java application using /opt/jboss/container/java/run/run-java.sh ...
INFO exec  java -Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 -XX:+UseParallelGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:+ExitOnOutOfMemoryError -cp "." -jar /deployments/quarkus-run.jar 
Listening for transport dt_socket at address: 5005
__  ____  __  _____   ___  __ ____  ______ 
 --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ 
 -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \   
--\___\_\____/_/ |_/_/|_/_/|_|\____/___/   
2023-02-21 19:39:30,919 WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.keycloak.devservices.enabled" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2023-02-21 19:39:30,919 WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.oidc.auth-server-url" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2023-02-21 19:39:31,637 INFO  [com.raj.sup.sit.AppLifecycleBean] (main) The application is starting...published staged archived /var/www/artifact /var/www/upload /var/www/orgfiles
WARNING: duplicate route registered for RenardeFormLoginController.login
2023-02-21 19:39:31,701 INFO  [io.quarkus] (main) qute-support-site 1.0.0-SNAPSHOT on JVM (powered by Quarkus 2.16.1.Final) started in 0.950s. Listening on: http://0.0.0.0:8080
2023-02-21 19:39:31,702 INFO  [io.quarkus] (main) Profile prod activated. 
2023-02-21 19:39:31,702 INFO  [io.quarkus] (main) Installed features: [cdi, hibernate-validator, mailer, narayana-jta, qute, reactive-routes, renarde, resteasy-reactive, resteasy-reactive-jackson, resteasy-reactive-qute, security, smallrye-context-propagation, smallrye-jwt, smallrye-openapi, swagger-ui, vertx]

I think something is missing?

Expected behavior

To be able to connect to the docker container with the debugger

Actual behavior

Get an error:

Attaching to localhost:5005
handshake failed - connection prematurally closed

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

JDK 17

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.16.1-Final

Build tool (ie. output of mvnw --version or gradlew --version)

Maven

Additional information

No response

[geoand]

You are correct!

#31332 should address the issue

[tmulle]

@geoand Thanks for the tip!

Adding -e JAVA_DEBUG_PORT=*:5005 to my command line provides the proper output and I can now connect to the docker instance via the Remote Debugging port.

My command line:
docker run -i --rm -p 5005:5005 -p 8080:8080 -e JAVA_DEBUG_PORT='*:5005' -e JAVA_DEBUG=true ....

Output from Docker:

Starting the Java application using /opt/jboss/container/java/run/run-java.sh ...
INFO exec  java -Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005 -XX:+UseParallelGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:+ExitOnOutOfMemoryError -cp "." -jar /deployments/quarkus-run.jar
Listening for transport dt_socket at address: 5005

[geoand]

👌

[tmulle]

@geoand Quick question on this topic of Dockerfile.

Can you tell me why you use USER=185 when building the docker images? Is that a special user?

I noticed it in the .JVM and .LEGACY versions of the file.

# We make four distinct layers so if there are application changes the library layers can be re-used
COPY --chown=185 target/quarkus-app/lib/ /deployments/lib/
COPY --chown=185 target/quarkus-app/*.jar /deployments/
COPY --chown=185 target/quarkus-app/app/ /deployments/app/
COPY --chown=185 target/quarkus-app/quarkus/ /deployments/quarkus/

EXPOSE 8080
EXPOSE 5005

USER 185
...

[geoand]

I can't say I know