Debugging our code with PhpStorm and Xdebug (with Xdebug installed in a docker-compose service container).Setting up the PhpStorm IDE so we can start and stop our docker-compose containers from within the IDE.In this article we'll go through the following: I am hoping this resource can be a good reference for myself and for others who might run into the same issues that I ran into. I decided to write this article because I was frustrated by how difficult it was to find all the information I needed to make these technologies work well together in a single article. Setup PHPStorm to run PHPUnit tests within docker container.We can see that in the configuration we've specified it to connect to the remote JVM using the 5005 port. So the above command starts our Docker container, and we can now configure remote debugging configuration to connect to it: In the JAVA_TOOL_OPTIONS we pass the value -agentlib:jdwp=transport=dt_shmem,address=,server=y,suspend=n to allow the Java process to start a JDB debug session and pass the value address=*:5005 to specify that 5005 will be our remote debugging port.
We are using the -d extension for running docker in detached mode and -e for passing JAVA_TOOL_OPTIONS as an environment variable to the Java process. Apart from the normal HTTP port, which is 8080, we are also mapping an additional port, 5005, for remote debugging using the -p extension. Here docker-java-jar is our image name, and latest is its tag. If we were using Java 11, we'd use this command instead: docker run -d -p 8080:8080 -p 5005:5005 -e JAVA_TOOL_OPTIONS="-agentlib:jdwp=transport=dt_socket,address=*:5005,server=y,suspend=n" docker-java-jar:latest Docker run -d -p 8080:8080 -p 5005:5005 -e JAVA_TOOL_OPTIONS="-agentlib:jdwp=transport=dt_socket,address=5005,server=y,suspend=n" docker-java-jar:latest
0 kommentar(er)
