Problem 1)

After firing up the example infrastructure services and then compiling and run travel service in dev mode the following error is seen.

Kogito Data Index Dev Service starting: 2023-03-19 16:04:41,962 ERROR [🐳 .io/.35]] (build-46) Could not start container: com.github.dockerjava.api.exception.InternalServerErrorException: Status 500: {"message":"driver failed programming external connectivity on endpoint pensive_haibt (a55b2ac9061a9282023-03-19 16:04:41,962 ERROR [🐳 .io/.35]] (build-46) Could not start container: com.github.dockerjava.api.exception.InternalServerErrorException: Status 500:

{"message":"driver failed programming external connectivity on endpoint pensive_haibt (a55b2ac9061a92859b2de40dbfa30ed692d4aac5ef38080e47133846f72b731b): Bind for 0.0.0.0:8180 failed: port is already allocated"}

g.testcontainers.shaded.com.github.dockerjava.core.exec.StartContainerCmdExec.execute(StartContainerCmdExec.java:31) 

This can be worked around by setting quarkus.kogito.devservices.enabled=false in application.properties

Problem 2)

With quarkus.kogito.devservices.enabled=false set for both the travels and visas services the following error is seen for the 2nd service to start

2023-03-19 16:08:46,991 ERROR [io.qua.grp.run.GrpcServerRecorder] (vert.x-eventloop-thread-0) Unable to start the gRPC server
2023-03-19 16:08:47,056 ERROR [io.qua.run.Application] (Quarkus Main Thread) Port 9000 seems to be in use by another process. Quarkus may already be running or the port is used by another application.

The 2nd service grpc server conflicts with the 1st service. The workaround is to change the port number in application.properties e.g.  quarkus.grpc.server.port=9010