-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nomad Docker driver silently discards auth when no key found #1662
Comments
Perhaps another option might be to mirror native docker behavior in auth key selection, since the lack of parity there was one of the other unexpected results |
Can you expand on how they are treated differently? |
When using the docker binary and passing the auths config file, it uses the |
Here is an example of a configuration file which worked with docker binary but not nomad:
|
Would an |
I think we can do a bit better job parsing the key in the docker driver |
@dadgar So would it need to be prefixed with |
@gliptak Yep that would be the first thought. I want to see how docker does it itself too |
WooHoo!! Thank you @dadgar |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
0.4.1-rc1
Operating system and Environment details
Ubuntu 16.04
Docker 1.12.0
Issue
When Nomad is configured to use docker authentication credentials through the use of the
docker.auth.config
driver option, but no auth key exists for the requested image, it silently falls back.Expected Behavior
A debug message is logged.
I ran into this while trying to debug why my private repo credentials were not working under Nomad. They worked when interacting Docker directly. It seems that Docker does not mandate the use of the
https://
prefix in the auths config for SSL repos, but Nomad does. In addition to debug logging, an update to the docker documentation fordocker.auth.config
driver option to specify the requirement would have saved a lot of time.The text was updated successfully, but these errors were encountered: