-
Notifications
You must be signed in to change notification settings - Fork 297
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
Bug: JBoss Keycloack migrated from Dockerhub to Quay.io causing problems #483
Comments
@matheusvnm thanks for reporting that issue. I already wrote a fix and linked your issue. |
Thanks for the quick reply. Your implementation is very similar to the one I did in my personal project. I gave my 2 cents about your solution in the PR. Do you know when the changes will be released, @max-pfeiffer? |
alexanderankin
pushed a commit
that referenced
this issue
Mar 21, 2024
…ge supported version [16+ -> 18+] (#480) - jboss/keycloak is discontinued, adapting the official Docker image: https://quay.io/repository/keycloak/keycloak - switched to the latest image version with ARM support fixes #451 fixes #483 ![Screenshot 2024-03-15 at 12 42 29](https://github.com/testcontainers/testcontainers-python/assets/13573675/f82b9372-a94e-45c8-a47b-7ddb4c1c6a57)
bearrito
pushed a commit
to bearrito/testcontainers-python
that referenced
this issue
Mar 30, 2024
…ge supported version [16+ -> 18+] (testcontainers#480) - jboss/keycloak is discontinued, adapting the official Docker image: https://quay.io/repository/keycloak/keycloak - switched to the latest image version with ARM support fixes testcontainers#451 fixes testcontainers#483 ![Screenshot 2024-03-15 at 12 42 29](https://github.com/testcontainers/testcontainers-python/assets/13573675/f82b9372-a94e-45c8-a47b-7ddb4c1c6a57)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Recently, JBoss removed the Keycloak repository in DockerHub. The future Keycloack versions will be released on Quay.io, which can be seen here. Below stands the logs with errors related to the inexistent jboss/keycloack repository.
Problem with new Keycloak versions
Even though we can set a different image/tag in the
KeycloakContainer
, the problem remains as that the newer versions of Keycloak differ in API structure when it comes to health checks compared to older versions. In other words, the/auth
is not used anymore for readiness/startup checks (as can be seen here and here). Hence, when one first calls thestart()
function, theKeycloackContainer
component keeps waiting for an endpoint that does not exist anymore. After a while, theKeycloackContainer
crashes as it reaches the maximum number of trials or times out.To Reproduce
To reproduce the first error (missing
jboss/keycloak
repository): You must first have all the dependencies installed with poetry. After that just runpytest -s
in thekeycloak/tests
directory to see the first error occur.To reproduce the second error (connection timeout): : You must first have all the dependencies installed with poetry. Then you must change the test function (on
keycloak/tests/test_keycloak.py
) to pull the image from the new Keycloak repository, as described below.Finally, execute
pytest -s
in thekeycloak/tests
directory.Runtime environment
The setup I'm currently using for testing is described below
The text was updated successfully, but these errors were encountered: