squakez commented on issue #5080: URL: https://github.com/apache/camel-k/issues/5080#issuecomment-1899885012
That's really strange. Do a jvm build run correctly? Could you try to build any java Quarkus native application and try to deploy to the cluster manually? I have the feeling there is some incompatibilities between the hardware your cluster is running and the Quarkus logic. Also, just for the sake of testing, you can try to run the same experiment with Camel K version 2.2 that was released last week, although I think it's not going to change things as it seems a Quarkus runtime problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
