Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"AuthConfig" unrecognized field 'identitytoken' due config loading

See original GitHub issue

Hello, we got the issue, using latest version of “docker-java” while trying to load and parse DOCKER configuration file (“$HOME/.docker/config.json”).

It doesn’t accept the field ‘identitytoken’. I have noticed that you have ‘registrytoken’ field, which have been used since DOCKER API v1.22 version for the same purpose. I checked documentation, it was renamed there into --> ‘identytoken’ just in the next DOCKER API v1.23 version.

Here is some stacktrace for more detailed info:

Caused by: java.lang.IllegalArgumentException: Unrecognized field "identitytoken" (class com.github.dockerjava.api.model.AuthConfig), not marked as ignorable (6 known properties: "serveraddress", "username", "auth", "password", "email", "registrytoken"])
 at [Source: N/A; line: -1, column: -1] (through reference chain: java.util.LinkedHashMap["auths"]->java.util.LinkedHashMap["hostname"]->com.github.dockerjava.api.model.AuthConfig["identitytoken"])
	at com.fasterxml.jackson.databind.ObjectMapper._convert(ObjectMapper.java:3589)
	at com.fasterxml.jackson.databind.ObjectMapper.convertValue(ObjectMapper.java:3530)
	at com.fasterxml.jackson.databind.ObjectMapper.convertValue(ObjectMapper.java:3518)
	at com.github.dockerjava.core.AuthConfigFile.loadConfig(AuthConfigFile.java:120)

Looks, that should be enough to just rename ‘@JsonProperty("identitytoken")’.