Deployment of extension classes fail when Keycloak testcontainer runs on a remote docker host
See original GitHub issueFirst of great work on creating this very useful test container! I do however hit a bump. When the Keycloak testcontainer is spawned on a remote docker host, the extension classes are never deployed. I suspect it has to do with the addFileSystemBind
which is registered on the directory. This directory is not present on the host where the Keycloak testcontainer is running.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Keycloak Testcontainer fails due Timed out waiting for URL to ...
java - Keycloak Testcontainer fails due Timed out waiting for URL to be accessible (http://localhost:55127/auth should return HTTP 200) - Stack ...
Read more >Testcontainers for Java
Testcontainers for Java is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or ...
Read more >Problem running tests on Azure Pipelines #39 - GitHub
I have a few tests that use testcontainers-keycloak that work just fine locally (on macOS). However, on Azure Pipelines the tests fail.
Read more >Dev Services Overview - Quarkus
When DevServices is enabled Quarkus will attempt to automatically configure and start Keycloak when running in Dev or Test mode and when Docker...
Read more >Keycloak Testcontainers - openid-connect-workshop - GitBook
You will notice that running the tests will last some time due to starting the Keycloak docker container first. After the container started...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
see https://github.com/dasniko/testcontainers-keycloak/releases/tag/1.9.0
There are not much other possibilities if we need to copy the resources to the container. All tests are still green. With Keycloak.X I don’t copy all the single files from the directory, but create a .jar archive on the fly first and copy this file to the container (due to requirements in KC.X and the Quarkus architecture). Tests work also for KC.X.