Suggestion: docker_registry saves auth token for future use

[cbreden]

docker_registry seems to only set an auth header for docker commands to be used during the chef run.

Proposing exposing an action (possibly :enable) that would permanently set the auth for future docker commands outside of the chef context. Example:

# cat .docker/config.json
{
        "auths": {
                "https://index.docker.io/v1/": {
                        "auth": "<GENERATED_AUTH_TOKEN_HERE>"
                }
        },
        "HttpHeaders": {
                "User-Agent": "Docker-Client/17.09.0-ce (linux)"
        }
}

Would this be a supported use case for the docker cookbook? That block could likely be managed with the line cookbook as opposed to a template file if other sources are touching config.json.

[feld]

I was surprised to learn this is not the default behavior

[damacus]

We should probably document this. Given there are many auth methods I'm inclined to say it's an exercise for the reader.