-
-
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
Is there anything I could do to fix the warning "Failure when attempting to lookup auth config" ? #1399
Comments
I found the same issue: When runs on local: When runs on Docker: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this. |
I'm getting the same error when running Testcontainer in a GitLab CI/CD environment (docker in docker):
And then tests fail. Is there anything I can do? |
That particular message is not a problem - it's simply saying that you don't have any credentials set for Please disregard that and look at other possible causes if you have test failures! I think we'd welcome a PR to clarify the wording for this log statement! |
I also am having this problem when using Bitbucket piplines, this is from the logs : 019-10-09 22:13:40,251 INFO o.t.d.DockerClientProviderStrategy [main] Will use 'okhttp' transport 2019-10-09 22:13:40,786 INFO o.t.DockerClientFactory [main] Docker host IP address is localhost Figured out my problem.. upgrade. see also ticket #700 |
Hi @rnorth ! Agreed, the warning is "harmless", meaning, nothing is actually wrong. This does, however, create extra build output which devs need to read and think about. Is there a way to suppress it? A property setting or something ... ? I'm scanning GitHub, and to look at the source of the warning ( testcontainers-java/core/src/main/java/org/testcontainers/utility/RegistryAuthLocator.java Line 135 in 9c320ee
lookupAuthConfig , nothing obvious jumps out at me.
|
Seems that maybe 'warn' is too important a level for this message in most circumstances. I have several of these warnings pertaining to Ryuk which I'm not expecting I'm using. |
I think we could consider changing it. Perhaps to INFO level, plus make the message clearer that this is probably not a problem. WDYT? |
Is this already done? Shall I make it info and raise the PR? |
@DevilzOwn I don't think it's been changed. If you'd be able to have a look and raise a small PR if necessary, I'd be grateful! Thanks |
Hello,
I'm running Testcontainer with maven on Ubuntu 17.04. It works but I get the warning below in bold every time. Is there something that I can do to fix it? Thanks so much!
11:14:50.379381-INFO Loaded org.testcontainers.dockerclient.ProxiedUnixSocketClientProviderStrategy from ~/.testcontainers.properties, will try it first
11:14:50.427417-INFO Will use 'okhttp' transport
11:14:50.883633-INFO Found Docker environment with local Unix socket (via TCP proxy)
11:14:50.885215-INFO Docker host IP address is localhost
11:14:51.012482-INFO Connected to docker:
Server Version: 17.12.0-ce
API Version: 1.35
Operating System: Ubuntu 17.04
Total Memory: 15934 MB
11:14:51.041070-WARN Failure when attempting to lookup auth config (dockerImageName: [Ljava.lang.Object;@63a65a25, configFile: {}. Falling back to docker-java default behaviour. Exception message: {}
11:14:51.571326-INFO Ryuk started - will monitor and terminate Testcontainers containers on JVM exit
ℹ︎ Checking the system...
✔ Docker version should be at least 1.6.0
✔ Docker environment should have more than 2GB free disk space
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.698 sec
The text was updated successfully, but these errors were encountered: