[docker-compose] distro not working properly ?

[hanyEthan]

Environment - Windows 10 pro / Docker for windows v20.10.2 / Google Chrome 87.0.4280.141
ApiCurio release - latest on Master branch (on the time of this comment)
Issue description:

we have been trying to test ApiCurio on our local Docker compose to evaluate it, as we have been hearing good feedback about it so far, but we are having difficult time setting it up using its Docker Compose distro ...

1. docker-compose distro is not running correctly due to an issue connecting to mysql without SSL.
2. quarkus docker-compose has been installed correctly
   • but not initially, as we had to replace this string in the .env file in order for Apicurio to integrate with the auth service correctly ...
     • APICURIO_KC_AUTH_URL=http://192.168.1.40:8090/auth/realms/apicurio replaced with APICURIO_KC_AUTH_URL=http://192.168.1.40:8090/auth
   • and all 3 portals opened correctly after that (keycloack, microcks, & Apicurio)
   • but Apicurio portal couldn't work with its api due to CORS issue
     

are we missing any configurations ?

Thank you.

[carlesarnal]

Hi @hanyEthan,

Regarding the docker-compose-distro this is the distro that you should use right now and a potential workaround for what you're describing can be found here.

Regarding the quarkus-compose-distro, the APICURIO_KC_AUTH_URL value in the .env is correct since that's the value that the quarkus image expects. That said since that distro isn't part of any release the images aren't publicly available at this moment and therefore this distro should not be used. If you still want to try the quarkus distro I'll be more than happy to give you some instructions on how to get it up & running (basically you'll need to build the images locally).

[hanyEthan]

Thank you so much @carlesarnal for your response.

• i'll re-test the recommended distro today with the suggested workaround, and i'll let you know.
• based on the results, we will see if we need to try the quarkus-compose-distro or not.

thank you again.

[hanyEthan]

Hi @carlesarnal,

• i tried the suggested workaround, and it worked (thank you).

• but it seems that i'm facing another issue with the auth service configuration, preventing both microcks and apicurio from starting.
  
  
  
  

• did we miss something else ?

thank you for your support.

[carlesarnal]

Hi @hanyEthan, afaik, no, you aren't missing anything. Could you please share the server log?

[hanyEthan]

hi @carlesarnal, thank you for replying,

• we have restarted all configurations, and retried again, this time, the ApiCurio system error disappeared (we didn't know why),
• but the microcks is still having the same auth issue.
• these are the microcks realm config, and logs for trying to open it, and then, trying to integrate with it configs & logs.zip.

thank you again,

[carlesarnal]

hi @hanyEthan, thanks, I'll take a look and try to reproduce this issue.

[carlesarnal]

Hi @hanyEthan, I'm glad you raised this cause it led me to find a bug in the docker-compose distro. We had a problem with the microcks realm template, causing the redirect URI to be invalid. I've linked a PR that should fix the issue.

Also, as a side note, you should access the applications using your host IP, using localhost will lead you to the same invalid_url error.

Thanks!

[hanyEthan]

thank you @carlesarnal, the installation and auth are working properly now.
we will continue our evaluation, and will report any blockers.