gradle-docker-plugin: Invalid Auth config file error Docker 17.06.0-ce-mac18 (18433)

I’ve been using this plugin absolutely fine until today.

I just had docker on my machine auto-update and thought nothing of it.

Then I ran my build and I’m now getting the following exception:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':EventManagement:MessageBroker:pullRabbitmq'.
> Failed to parse dockerCfgFile

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':EventManagement:MessageBroker:pullRabbitmq'.
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:98)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:68)
        at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62)
        at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
        at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)
        at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:46)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:51)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
        at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.execute(DefaultTaskGraphExecuter.java:236)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.execute(DefaultTaskGraphExecuter.java:228)
        at org.gradle.internal.Transformers$4.transform(Transformers.java:169)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:61)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:228)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:215)
        at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:77)
        at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:58)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
        at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:46)
Caused by: com.github.dockerjava.api.exception.DockerClientException: Failed to parse dockerCfgFile
        at com.github.dockerjava.core.DefaultDockerClientConfig.effectiveAuthConfig(DefaultDockerClientConfig.java:268)
        at com.github.dockerjava.core.DockerClientImpl.pullImageCmd(DockerClientImpl.java:215)
        at com.github.dockerjava.api.DockerClient$pullImageCmd.call(Unknown Source)
        at com.bmuschko.gradle.docker.tasks.image.DockerPullImage.runRemoteCommand(DockerPullImage.groovy:49)
        at com.bmuschko.gradle.docker.tasks.AbstractDockerRemoteApiTask$_runReactiveStream_closure1.doCall(AbstractDockerRemoteApiTask.groovy:57)
        at com.bmuschko.gradle.docker.utils.DockerThreadContextClassLoader.withClasspath(DockerThreadContextClassLoader.groovy:55)
        at com.bmuschko.gradle.docker.utils.ThreadContextClassLoader$withClasspath.call(Unknown Source)
        at com.bmuschko.gradle.docker.tasks.AbstractDockerRemoteApiTask.runInDockerClassPath(AbstractDockerRemoteApiTask.groovy:62)
        at com.bmuschko.gradle.docker.tasks.AbstractDockerRemoteApiTask$runInDockerClassPath.callCurrent(Unknown Source)
        at com.bmuschko.gradle.docker.tasks.AbstractDockerRemoteApiTask.runReactiveStream(AbstractDockerRemoteApiTask.groovy:56)
        at com.bmuschko.gradle.docker.tasks.AbstractReactiveStreamsTask.start(AbstractReactiveStreamsTask.groovy:50)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
        at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.doExecute(DefaultTaskClassInfoStore.java:141)
        at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134)
        at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:123)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:692)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:675)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.execute(ExecuteActionsTaskExecuter.java:115)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.execute(ExecuteActionsTaskExecuter.java:109)
        at org.gradle.internal.Transformers$4.transform(Transformers.java:169)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:56)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:109)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:90)
        ... 20 more
Caused by: java.io.IOException: Invalid Auth config file
        at com.github.dockerjava.core.AuthConfigFile.loadConfig(AuthConfigFile.java:146)
        at com.github.dockerjava.core.DefaultDockerClientConfig.effectiveAuthConfig(DefaultDockerClientConfig.java:266)
        ... 43 more

I’ve tried with both com.bmuschko:gradle-docker-plugin:3.0.8 and com.bmuschko:gradle-docker-plugin:3.0.7 and both have the same problem.

I’m not really sure if this is a bug with the plugin or the underlying library. I’m also not really certain where to start debugging this problem; any pointers in the right direction would be helpful.

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 27 (5 by maintainers)

Most upvoted comments

This issue happens on Docker for Mac Version 18.06.1-ce-mac73 (26764). Removing ~/.docker/config.json fixes the problem.

rakeshyoga on Sep 28, 2018

LOVELY!!! This seems to have completely solved my problem! My builds are running again! Woot!

JLLeitschuh on Jul 7, 2017

@MattMcName yeah that appears to be the case. Let me reach out to those guys and see if I can get them to do another release.

cdancy on Jul 5, 2017

{"credsStore":"wincred"} For what it’s worth, if I delete or rename the config.json file, all is well.

ghost on Aug 14, 2017

Something got fudged up with our release process and it appears that 3.0.11 was released instead?!? Folks feel free to give that a go while I try to figure out what is going on…

cdancy on Jul 7, 2017

3.0.12 is out as of 5th of july time for a 3.0.10 release of your plugin 😉

in the meantime and those who don’t want to update your plugin: Disable the secret store in keychain: https://github.com/docker-java/docker-java/issues/806#issuecomment-313023284

childnode on Jul 7, 2017

Still broken on v3.0.9 here. The docker-java issue is marked for 3.0.12, but it looks like it hasn’t been released yet?

MattMcNam on Jul 5, 2017

@menduz fix is already in master. We’re looking to do a release shortly (hopefully within the next few days). Will post back here when we do.

cdancy on Jul 2, 2017

@cdancy FAILURE! upgrade to v.3.0.9, the problem remains.

waincent on Jul 5, 2017