Question - Trying to run the issuer kit locally but I see a blank page.
dinbtechit opened this issue · comments
I am trying to run issuer-kit locally but see a blank page
I followed the steps as specified -> https://github.com/bcgov/issuer-kit#local-mode
Note - I have successfully running von-network (http://localhost:9000)
- manage build (Note - I did see one error - as shown below)
Building issuer-kit-api image using centos/nodejs-12-centos7 as base... error: Unable to load docker config: json: cannot unmarshal string into Go value of type docker.dockerConfig ---> Installing application source ... ---> Installing all dependencies ** REST output seems pretty successful**
- manage start (Looks like everything came up successfully)
. . . Creating issuer-kit_issuer-admin_1 ... done Creating issuer-kit_wallet_1 ... done Creating issuer-kit_tails-server_1 ... done Creating issuer-kit_db_1 ... done Creating issuer-kit_keycloak-db_1 ... done Creating issuer-kit_maildev_1 ... done Creating issuer-kit_issuer-web_1 ... done Creating issuer-kit_api_1 ... done Creating issuer-kit_agent_1 ... done Creating issuer-kit_keycloak_1 ... done
Output:
- issuer-admin:
- Issuer-web
Not sure if I am missing anything. Any help is massively appreciated!
The steps you completed seem correct. Would you be able to check the browser console for errors for both frontends and post the result?
oh! looks like the Keycloak service is not running. I see one error not sure if that has something to do with that.. Also, I am running this on mac. Perhaps that's something to do with the error?
keycloak_1 | 11:43:30,560 ERROR [org.jboss.modcluster] (ServerService Thread Pool -- 60) MODCLUSTER000034: Failed to start advertise listener: java.net.SocketException: Protocol not available (Error setting socket option)
manage LOGS:
keycloak_1 | 11:43:30,560 ERROR [org.jboss.modcluster] (ServerService Thread Pool -- 60) MODCLUSTER000034: Failed to start advertise listener: java.net.SocketException: Protocol not available (Error setting socket option)
keycloak_1 | at java.base/java.net.PlainDatagramSocketImpl.socketSetOption0(Native Method)
keycloak_1 | at java.base/java.net.PlainDatagramSocketImpl.socketSetOption(PlainDatagramSocketImpl.java:91)
keycloak_1 | at java.base/java.net.AbstractPlainDatagramSocketImpl.setOption(AbstractPlainDatagramSocketImpl.java:352)
keycloak_1 | at java.base/java.net.MulticastSocket.setInterface(MulticastSocket.java:477)
keycloak_1 | at org.jboss.mod_cluster.core@1.4.1.Final//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.init(AdvertiseListenerImpl.java:151)
keycloak_1 | at org.jboss.mod_cluster.core@1.4.1.Final//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.start(AdvertiseListenerImpl.java:161)
keycloak_1 | at org.jboss.mod_cluster.core@1.4.1.Final//org.jboss.modcluster.ModClusterService.init(ModClusterService.java:165)
keycloak_1 | at org.wildfly.mod_cluster.undertow@21.0.2.Final//org.wildfly.mod_cluster.undertow.UndertowEventHandlerAdapterService.start(UndertowEventHandlerAdapterService.java:83)
keycloak_1 | at org.wildfly.clustering.service@21.0.2.Final//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
keycloak_1 | at java.base/java.lang.Thread.run(Thread.java:829)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
keycloak_1 |
....
keycloak_1 | 11:43:37,790 ERROR [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 62) failed setting interface to /172.20.0.11: java.net.SocketException: Protocol not available (Error setting socket option)
keycloak_1 | 11:43:37,797 ERROR [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 62) failed setting interface to /172.20.0.11: java.net.SocketException: Protocol not available (Error setting socket option)
keycloak_1 | 11:43:37,806 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalStateException: java.net.SocketException: Protocol not available
keycloak_1 | at org.wildfly.clustering.service@21.0.2.Final//org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:66)
keycloak_1 | at org.wildfly.clustering.service@21.0.2.Final//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
keycloak_1 | at java.base/java.lang.Thread.run(Thread.java:829)
keycloak_1 | at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
keycloak_1 | Caused by: java.lang.IllegalStateException: java.net.SocketException: Protocol not available
keycloak_1 | at org.jboss.as.clustering.jgroups@21.0.2.Final//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116)
keycloak_1 | at org.jboss.as.clustering.jgroups@21.0.2.Final//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58)
keycloak_1 | at org.wildfly.clustering.service@21.0.2.Final//org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:63)
k
keycloak_1 | 11:43:39,249 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
keycloak_1 | ("subsystem" => "jgroups"),
keycloak_1 | ("channel" => "ee")
keycloak_1 | ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.clustering.jgroups.channel.ee" => "java.lang.IllegalStateException: java.net.SocketException: Protocol not available
keycloak_1 | Caused by: java.lang.IllegalStateException: java.net.SocketException: Protocol not available
keycloak_1 | Caused by: java.net.SocketException: Protocol not available"}}
keycloak_1 | 11:43:40,206 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: Keycloak 12.0.4 (WildFly Core 13.0.3.Final) started (with errors) in 37754ms - Started 493 of 926 services (48 services failed or missing dependencies, 684 services are lazy, passive or on-demand)
...i
Ok this appears like an issue with Mac M1 chip and keycloak docker container. I was able to resolve the above error by building docker image locally.
Steps:
Clone Keycloak containers repository: git clone git@github.com:keycloak/keycloak-containers.git
Open server directory (cd keycloak-containers/server
)
Checkout at desired version, eg. git checkout 12.0.4
Build docker image docker build -t jboss/keycloak:12.0.4 .
Alternatively, You can also use this script to build the image:
#/bin/zsh
VERSION=12.0.4 # set version here
cd /tmp
git clone git@github.com:keycloak/keycloak-containers.git
cd keycloak-containers/server
git checkout $VERSION
docker build -t "jboss/keycloak:${VERSION}" .
Credits: docker/for-mac#5310 (comment)
Voila! and it works!
@dinbtechit thanks for troubleshooting this! I'm surprised the host system architecture would cause issue, interesting!
You may also want to try and updating the keycloak image to a later version in docker-compose.yml
rather than building it locally - it might be something that was resolved in a more recent release.
@esune - Certainly! I can try that. On a completely side note - I ran into this issue -> #208 (comment). Do you have any suggestion on how to resolve that?
@esune - Certainly! I can try that. On a completely side note - I ran into this issue -> #208 (comment). Do you have any suggestion on how to resolve that?
Responding on the other thread - no idea for now though.