Using Docker Daemon Registry (Default) may result in failure to authenticate [EBZ#494776] ----------------------------------------------------------------------------------------- Key: ERT-222 URL: https://issues.jboss.org/browse/ERT-222 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Assignee: Roland Grunberg Labels: Docker, bzira For now the expectation should be that "Docker Daemon Registry (Default)" is accessing the default configured registry with no authentication credentials. We still have : try { builder.authConfig(AuthConfig.fromDockerConfig().build()); } catch (Exception e) { // AuthConfig can't be found, continue } in the DockerClientFactory as part of the standard docker client creation. If the user actually has a config.json file in one of the searched locations, it'll be used. I think for now we should not support this because it's not really clear for the user that we're attempting to authenticate for them. We don't even restrict the auth credentials to jusy those matching the server name.