You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more a question than an issue, but it might result as an enhancement.
I am working on a Spring Boot POC application that I build in native using Spring Boot buildpack. During the native image build process, there is a NullPointerException in a GraalVM class I would like to investigate.
The native-image argument --debug-attach allows me to attach a debugger during the image building but I am unable to connect, I presume, because the port number is not exposed. I may be underestimating the difficulty, but would it be possible to expose the port mentioned in the aforementioned argument ?
Thank you in advance of your advice
The text was updated successfully, but these errors were encountered:
The challenge is going to be getting network access, as you said. I don't thing that Spring Boot's build commands or pack allow this. They both run your build inside a container, but there are no options I'm aware of to expose ports on those build containers.
You might be able to use a process similar to this one to run the buildpack in a VM or container that you create, thereby allowing you to expose ports. It's a bit of work though, so you'll have to determine if that's worth it for you.
I don't know if this would be feasible, but you should be able to docker ps and docker exec into the build container. Most of the time they are short-lived so this would be difficult, but with native image, the builds take a while so if you're quick you might be able to exec in and inspect over the CLI.
Hi there,
This is more a question than an issue, but it might result as an enhancement.
I am working on a Spring Boot POC application that I build in native using Spring Boot buildpack. During the native image build process, there is a NullPointerException in a GraalVM class I would like to investigate.
The native-image argument
--debug-attach
allows me to attach a debugger during the image building but I am unable to connect, I presume, because the port number is not exposed. I may be underestimating the difficulty, but would it be possible to expose the port mentioned in the aforementioned argument ?Thank you in advance of your advice
The text was updated successfully, but these errors were encountered: