-
Notifications
You must be signed in to change notification settings - Fork 23
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
Update container images to those that support the ARM architecture #319
Conversation
Signed-off-by: Kyle Aure <[email protected]>
@rieckpil any idea why Wildfly is failing here? We got a 404 at the endpoint 00:17:44,323 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: '/myservice' for server 'default-server'
00:17:44,373 INFO [org.jboss.as.server] (ServerService Thread Pool -- 45) WFLYSRV0010: Deployed "myservice.war" (runtime-name : "myservice.war")
00:17:44,402 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
00:17:44,405 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
00:17:44,405 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
00:17:44,408 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 30.0.0.Final (WildFly Core 22.0.1.Final) started in 2317ms - Started 365 of 587 services (322 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml I had to fix this by going down from version 30.0.0 to version 26.1.2 |
4b543c2
to
57af549
Compare
Signed-off-by: Kyle Aure <[email protected]>
Signed-off-by: Kyle Aure <[email protected]> Co-authored-by: asjervanasten <[email protected]>
Signed-off-by: Kyle Aure <[email protected]>
57af549
to
75c66de
Compare
Signed-off-by: Kyle Aure <[email protected]> Co-authored-by: asjervanasten <[email protected]>
@KyleAure nice work |
Fixes #317
Fixes #316