quarkus-quickstart | This quickstart will show | Identity Management library

It's due to the docker link variables that kubernetes mimics for Service names in scope; it bites people a lot when they have generically named services such as { apiVersion: v1, kind: Service, metadata: { name: http }, ... as it will cheerfully produce environment variables of the form HTTP_PORT=tcp://10.233.12.82:80 in the Pod, and things such as Spring boot or evidently Quarkus which coerce env-vars into configuration overrides can cause the exact outcome you're experiencing

The solution is (a) don't name Services with bland names (b) "mask off" the offensive env-vars for the Pod:

The problem is in Uni.createFrom().item(ioSimulation(name)). You synchronously call ioSimulation before the Uni is created.

You should at least use the Supplier variant: Uni.createFrom().item(() -> ioSimulation(name)). That should help.

As suggested by the comments this seems to be a bug (https://github.com/quarkusio/quarkus/issues/16619). It works with the AttributeConver:

Fruit.java:

If you want to have a clean response after every method call, you can try declaring the arraylist inside the method.

It doesn't work because your are using native mode and the io.jsonwebtoken library seems that does not support it.

Quarkus does its best to integrate libraries and make them work with native mode, by adding the pieces required by native mode. For native mode limitations, please check this link: https://www.graalvm.org/reference-manual/native-image/Limitations/.

Please check Quarkus JWT support that works with native mode: https://quarkus.io/guides/security-jwt.

If you really want to keep using io.jsonwebtoken you may need to provide additional metadata to the native image build: https://quarkus.io/guides/writing-native-applications-tips.

By default, OpenTracing doesn't log automatically into span logs, only important messages that Jaeger feels it needs to be logged and is needed for tracing would be there :). The idea is to separate responsibilities between Tracing and Log management, Check this GitHub discussion.

An alternative would be to use centralized log management and print traceId & spanId into your logs for troubleshooting and correlating logs and tracing.

The X-Ray SDK uses the Apache commons logging library to emit log messages. It takes this dependency transitively from the AWS SDK. I'm not familiar with the quarkus library, but the only reason that I can think of that would cause this error is if a pom.xml somewhere is explicitly excluding the Apache commons logging library from being pulled in transitively. The remedy that should work is to add the dependency to your classpath manually:

Updating Docker Desktop for Windows to the latest version (2.3.0.3) fixed my issue.

There are 2 basic modes that a Quarkus application can be deployed:

1. As a standard Java application (executable jar with libraries on the classpath)
2. As a native executable which can be built using GraalVM

Based on the output snippet you posted, it looks like you're running the application as a regular Java app.

If you deploy your application as a standard Java app, then you can "deploy" Quarkus anywhere you can run an executable jar (bare metal, containers, etc).

If you do the extra step of compiling your application into a native executable (which is not mandatory BTW) then your app can only be deployed on an OS that is compatible with the native executable -- which is where containers really comes in handy.

If you put either the Java app or the native executable app inside a container, you can deploy the container anywhere that supports running containers.