-
-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to launch on Apple M1 #43
Comments
Hi @Alejandro-J-Caputto, |
You should not ask Docker request here. Please head here: https://docs.docker.com/desktop/mac/apple-silicon/ |
@lucasff thank you |
you could use this image |
Hi @eduardosanzb, |
@garronej yes! So far I'm just starting to understand the framework, but definitely I'm able to run custom template only changing the Dockerfile
And then running the sh script. definitely there are some errors popping out in the console! Nevertheless I was able to run the template; so I decided to ignore those errors for now. (eventually I'll deploy in a linux server). |
Thank you for your answer. Good to know. |
@garronej I build keycloak v15 for M1 if you need it! |
Thank you for taking your time to answer. I am working again with keycloak and of course using keycloakify 😄 . Amazing job!! It rocks 🚀 |
Sorry I just ordered a new MacBook now so I didn't get the chance to test on M1 but I will eventually and address any problem that might arise. |
I reopen, now that I got an M1 I'll try to make it work out of the box. |
Works out of the box now. Thank you @eduardosanzb 🙏🏻 |
@eduardosanzb @Alejandro-J-Caputto. I need your help 🙏🏻 I can't make it work on my M1. Screen.Recording.2022-04-08.at.15.23.10.movI get this 404, I can't figure out why. How did you make it work? The last version, when you run Could you try and tell me if it works on your machine, maybe with keycloakify_demo_app? I am stuck, I can't spend a whole day debugging this and, in the meantime, I can't deal with new issues coming up (#86 #85) If you could give me a hand on this, it would be highly appreciated! |
Ok I found a solution 😄 |
Full M1 compat in 4.7.4 |
Hello,
I have build a Keycloak theme but when I try to launch the docker container I am facing the following issues (see below). Do you know how could I solve this problem? Thank you
09:31:08,790 ERROR [org.jboss.modcluster] (ServerService Thread Pool -- 60) MODCLUSTER000034: Failed to start advertise listener: java.net.SocketException: Protocol not available (Error setting socket option) at java.base/java.net.PlainDatagramSocketImpl.socketSetOption0(Native Method) at java.base/java.net.PlainDatagramSocketImpl.socketSetOption(PlainDatagramSocketImpl.java:91) at java.base/java.net.AbstractPlainDatagramSocketImpl.setOption(AbstractPlainDatagramSocketImpl.java:352) at java.base/java.net.MulticastSocket.setInterface(MulticastSocket.java:477) at org.jboss.mod_cluster.core@1.4.1.Final//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.init(AdvertiseListenerImpl.java:151) at org.jboss.mod_cluster.core@1.4.1.Final//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.start(AdvertiseListenerImpl.java:161) at org.jboss.mod_cluster.core@1.4.1.Final//org.jboss.modcluster.ModClusterService.init(ModClusterService.java:165) at org.wildfly.mod_cluster.undertow@20.0.1.Final//org.wildfly.mod_cluster.undertow.UndertowEventHandlerAdapterService.start(UndertowEventHandlerAdapterService.java:83) at org.wildfly.clustering.service@20.0.1.Final//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
The text was updated successfully, but these errors were encountered: