Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Hi team,

I am using IntelliJ and integrated maven 3.9, Java Correto 21. My build for Microcks (even clean install) is failing and I am seeing in the logs that the docker connectivity is failing. The logs are showing

[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.015 s <<< FAILURE! -- in io.github.microcks.security.OAuth2AuthorizeClientProviderTest [ERROR] io.github.microcks.security.OAuth2AuthorizeClientProviderTest -- Time elapsed: 0.015 s <<< ERROR! java.lang.ExceptionInInitializerError at java.base/jdk.internal.misc.Unsafe.ensureClassInitialized0(Native Method) at java.base/jdk.internal.misc.Unsafe.ensureClassInitialized(Unsafe.java:1160) at java.base/java.lang.reflect.Field.acquireOverrideFieldAccessor(Field.java:1200) at java.base/java.lang.reflect.Field.getOverrideFieldAccessor(Field.java:1169) at java.base/java.lang.reflect.Field.get(Field.java:444) at org.testcontainers.junit.jupiter.TestcontainersExtension.getContainerInstance(TestcontainersExtension.java:252) at org.testcontainers.junit.jupiter.TestcontainersExtension.lambda$findSharedContainers$10(TestcontainersExtension.java:213) at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197) at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1708) at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921) at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682) at org.testcontainers.junit.jupiter.TestcontainersExtension.findSharedContainers(TestcontainersExtension.java:214) at org.testcontainers.junit.jupiter.TestcontainersExtension.beforeAll(TestcontainersExtension.java:54) at java.base/java.util.ArrayList.forEach(ArrayList.java:1596) Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=quay.io/keycloak/keycloak:26.0.0, imagePullPolicy=DefaultPullPolicy(), imageNameSubstitutor=org.testcontainers.utility.ImageNameSubstitutor$LogWrappedImageNameSubstitutor@4ee8ba7f) at org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1364) at org.testcontainers.containers.GenericContainer.logger(GenericContainer.java:671) at dasniko.testcontainers.keycloak.ExtendableKeycloakContainer.<init>(ExtendableKeycloakContainer.java:149) at dasniko.testcontainers.keycloak.KeycloakContainer.<init>(KeycloakContainer.java:28) at io.github.microcks.security.OAuth2AuthorizeClientProviderTest.<clinit>(OAuth2AuthorizeClientProviderTest.java:42) ... 17 more

What I did, was first to download the images (keycloak, Mongo and ryuk) manually and seeing that this issue is still there, I then added a few environment parameters in the Maven runner config as shown below
DOCKER_CONTEXT=desktop-linux;DOCKER_API_VERSION=1.52;DOCKER_HOST=unix:///Users/xxxxxxxxx/.docker/run/docker.sock

Unfortunately it still fails. Would anyone have a clue on why this is happening?

Cheers
Kris

You must be logged in to vote

Replies: 1 comment · 2 replies

Comment options

Hello,

is it the only stacktrace or exception message you have? If you're on MacOS, it could be a conflict between testcontainers and the api version of your Docker client... Are you on MacOS?

You must be logged in to vote
2 replies
@krisrr3
Comment options

Hi Laurent,

Yes just trying to setup on Mac. I did have it working on Windows before.

There is more to the stacktrace, but I guess I was looking for general guidance on things I missed as setup steps before running the build.

Cheers
Kris

@lbroudoux
Comment options

Check this one: https://stackoverflow.com/questions/79817033/sudden-docker-error-about-client-api-version
I had the same errors a few days ago when starting on a fresh Mac. It is solved with latest version of testcontainers lib but it's a breaking change and we must spend time upgrading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Morty Proxy This is a proxified and sanitized view of the page, visit original site.