Trying to get apicurio working with keycloak within a docker-compose environment

[abryant710]

I'm trying to get API Curio working in a docker-compose environment. I'm seeing the following errors in my apicurio-registry container:

2023-06-22 14:47:15 2023-06-22 04:47:15 WARN <> [null] (vert.x-eventloop-thread-1) OIDC Server is not available:: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: keycloak/192.168.176.4:8443
2023-06-22 14:47:15 Caused by: java.net.ConnectException: Connection refused
2023-06-22 14:47:15     at java.base/sun.nio.ch.Net.pollConnect(Native Method)
2023-06-22 14:47:15     at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
2023-06-22 14:47:15     at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946)
2023-06-22 14:47:15     at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
2023-06-22 14:47:15     at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
2023-06-22 14:47:15     at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
2023-06-22 14:47:15     at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
2023-06-22 14:47:15     at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
2023-06-22 14:47:15     at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
2023-06-22 14:47:15     at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
2023-06-22 14:47:15     at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2023-06-22 14:47:15     at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
2023-06-22 14:47:15     at java.base/java.lang.Thread.run(Thread.java:833)
2023-06-22 14:47:15 
2023-06-22 14:47:15 2023-06-22 04:47:15 WARN <> [null] (vert.x-eventloop-thread-1) OIDC server is not available at the 'https://keycloak:8443/auth/realms/registry' URL. Please make sure it is correct. Note it has to end with a realm value if you work with Keycloak, for example: 'https://localhost:8180/auth/realms/quarkus'
2023-06-22 14:47:15 2023-06-22 04:47:15 WARN <> [null] (vert.x-eventloop-thread-1) Tenant 'Default': 'OIDC Server is not available'. OIDC server is not available yet, an attempt to connect will be made duiring the first request. Access to resources protected by this tenant may fail if OIDC server will not become available

Keycloak starts up as expected and lets me do the base configuration, i.e., create realm called registry, create client called apicurio-registry, create roles and users for sr-admin, sr-developer, sr-readonly, etc. I'm then unable to access the web UI at https://localhost:8443/ui/ and get a blank white screen. It seems to me to be an issue with the connectivity between apicurio and keycloak within the network and specifically using the certificates for ssl.

import-certificate.sh.txt
docker-compose.yml.txt
Dockerfile.txt

My requirements are for the container environment to operate over https everywhere and to have keycloak provide an authentication layer. This should enable the web UI for apicurio to be used for schema registry management. Readonly access will also be necessary using the API for schema validation services by some other microservices.

[EricWittmann]

What is the order of startup? Is Keycloak coming up after the registry pod attempts to connect to it perhaps?