Skip to content
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

Notary should fail when being run in a script and no credentials provided #1184

Closed
dave-tucker opened this issue Jun 28, 2017 · 1 comment
Closed
Labels

Comments

@dave-tucker
Copy link

I'd like to use notary in a Makefile to check that an specific org/image:tag is signed.
There are cases where the image may not have yet been pushed and in these cases I would expect notary to exit 1 so I can push/sign the image in question.

For example, in LinuxKit, if a contributor where to add a new package called "foo", our Makefile would check:

notary -s https://notary.docker.io lookup docker.io/linuxkit/foo $(HASH)

but linuxkit/foo would not yet exist.

This appeared to hang forever, but when I ran the command manually I saw that notary was prompting for a Username: and Password:. My expection would be that if no credentials were provided then this command should fail.

/cc @riyazdf

@riyazdf
Copy link
Contributor

riyazdf commented Aug 1, 2017

closed by #1200

@riyazdf riyazdf closed this as completed Aug 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants