Private registry authorization problems about shepherd HOT 4 CLOSED

Ok I think I got a working solution...

1. I logged into the docker swarm master and did 'docker login' - this created a config.json
2. I copied the config.json and made a config on my swarm with it.
3. added a config to shepherd and mapped it to /root/.docker/config.json.

Hope this helps someone.

Note: There is a risk that the authentication token will expire at some point.

from shepherd.

Yeah, I think this is a unresolved problem. For a permanently working solution, we would probably need to pass the login credentials to the container so it could login to the registry before each update run. That would probably be a really useful change.

from shepherd.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from shepherd.

@mikesutton It's been a long time, but you might be pleased to know that registry authentication is integrated in the latest version.

from shepherd.