-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Enhancement]: Support TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE to be read from ~/.testcontainers.properties #8537
Comments
I would also like to use this feature. I have exactly the same use-case as @AndreasEK. Having to provide the env variable every time is very inconvenient (especially in the IDE). By the way, it's already implemented in Happy to implement this one if maintainers agree that it is a good idea. |
+1, I think the problem is in this piece: https://github.com/testcontainers/testcontainers-java/blob/main/core/src/main/java/org/testcontainers/DockerClientFactory.java#L164-L168 In I think it just a bug... |
Module
Core
Proposal
When I understood these correctly:
… on mac with colima, the environment variable
TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE
is required.This is a nuicance, when acceptance tests are run from the IDE, since then every run configuration has to include this env variable, or maybe you would have to create a template for it, etc. I tried to work around that situation by using
~/.testcontainers.properties
for it, but only when I set the actual environment variable, the tests work fine.Running Integration Tests only with properties
With only the
~/.testcontainers.properties
in place, ryuk cannot be detected:Running Integration Tests with TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE
After exporting
TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE
connection is refused:Running Integration Tests with TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE & TESTCONTAINERS_HOST_OVERRIDE
The text was updated successfully, but these errors were encountered: