Niko Köbler

Thanks for reporting. I just tried to reproduce this behavior, but unfortunately I can't enforce the same exception. When reading your posted stacktrace, this happens when actually trying to copy...

Closing this, as there was no further action in the last few months.

Hi @xgp this is one of the issues from the category _"having fun with resteasy dependencies"_, or, as I wrote one time in a commit message: _"fighting the resteasy dependency...

Your second "issue", starting multiple containers, is not related to the Keycloak Testcontainers. It's the way, the Testcontainers work: You declare your container instance as a class member. In this...

I can't really reproduce this behavior... But I see a coincidence with a similar error message when dealing with Docker containers on my machine, when there is e.g. not enough...

You can mitigate version conflicts with setting an explicit Keycloak image when creating the container, e.g. `new KeycloakContainer("quay.io/keycloak/keycloak:18.0.0");` This way, the testcontainer doesn't use the most recent default image, like...

Thanks for providing this. I made some comments to your code, please have a look at it. 🙂

Sorry, my fault. Didn't finish the review properly.

Everything is fine over here... My log output for reference: ``` ➜ testcontainers-keycloak-test git:(main) ✗ mvn clean package [INFO] Scanning for projects... [INFO] [INFO] -----------------< test:testcontainers-keycloak-test >------------------ [INFO] Building testcontainers-keycloak-test...

I sometimes encounter this error message `Failed to create a new filesystem for...` if there are other stopped/dangling Keycloak containers. Don't know exactly why, but removing them makes it work...