-
Notifications
You must be signed in to change notification settings - Fork 310
KeycloakContainer image #289
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
Comments
Do you have the full code for the test handy? It looks like there is a
|
Hi, yeah, I did't realize that I had two KeycloakContainer objects. I tried again with only kc but the output it's the same.
Output:
|
Would you be up for sending a PR with the failing test? Then we can ensure any changes we introduce address the problem you've encountered? |
Hi! Just wanted to add my 2 cents here since I'm looking at the library as an interesting alternative to sidecars in the pipeline as we need integration testing to test an update in the infrastructure. I haven't tested yet but I have a hunch this is happening because since versions 17 (which I believe is the latest in jboss repo) the Instead, by lookin at here, we can see how to enable the new health check endpoint and how to access it. Hope I was helpful :P |
I can confirm this. Using a bitnami/keycloak version 20 image the following error is thrown: |
This issue is already solved by #480. The solution was to update the health probes to the new versions of Keyclock that is presented in Quay.io repository. I believe this issues can be closed @tillahoffmann |
Thank you for the update @matheusvnm. Closing this one as #480 seems to have done the trick. |
Hi! I was trying to change from
jboss/keycloak
image toquay.io/keycloak/keycloak:latest
because the jboss repo is not longer supported. However, I don't know why, I'm getting TimeoutException during port mapping for container.Here I have the logs:
This is my tests:
The text was updated successfully, but these errors were encountered: