We now trigger the deployment of exploded extensions folders during container start
by copying a dynamically generated ".dodeploy" file.
Previously we mounted an external ".dodeploy" file into the container to trigger the exploded jar deployment, which did not work on some operating systems (OSX) when container reuse was used.
Added test-case for container reuse support
Excluded slf4j dependency to fix broken container logging
dasniko
commented
3 years ago
We now trigger the deployment of exploded extensions folders during container start by copying a dynamically generated ".dodeploy" file.
Previously we mounted an external ".dodeploy" file into the container to trigger the exploded jar deployment, which did not work on some operating systems (OSX) when container reuse was used.
Fixes #17
This supersedes the pull request https://github.com/dasniko/testcontainers-keycloak/pull/18