-
Notifications
You must be signed in to change notification settings - Fork 512
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 init without '-s' panics #1022
Comments
Properly not a duplicate #1016 |
@rikatz Could you please post the output of |
Sure:
|
It seems like also build with |
@rikatz: sorry to hear you're running into this - which notary binary are you using (linux/mac/built on your own)? I'm unable to repro on mac, so I'm wondering if it's a linux issue. Also, do you have any existing configuration in @HuKeping: where do you see the
|
Hi @riyazdf I suppose you get it from the trace of
I'm not very certain about that , but everytime I typed
which there is not such a message about |
@riyazdf I'm using the binary version for Linux/AMD64, and running on a CentOS 7.2.1511 I've tested on a fresh install Linux here (without the .notary directory) and the error happens. Note that when I use the correct command (./notary-Linux-amd64 --debug init -s "https://notary.docker.io" docker.io/rpkatz/nginx) the command goes well:
|
@rikatz: thanks for the information, I'm able to repro. The default value for the server is It seems that this is an issue with how cgo is looking up hosts without TLDs. For example you'll get the same panic with |
@riyazdf how to repro that |
@HuKeping: I downloaded the linux binary from our releases page to a fresh Ubuntu 16.04 box, and tried a The panic is not unique to the |
Ok it seems to be
I'm not sure how to move forward with this; I'm playing with different flags to disable parts of cgo for networking (ex: |
Fix released in |
Doing some tests here with notary (following this: https://docs.docker.com/notary/advanced_usage/) I've noticed that, when I forget to pass the '-s' argument the client panics, as the following:
Using the command with the '-s' argumment works fine. Probably notary should not panic, but print an error message and exit, right?
Thanks!
The text was updated successfully, but these errors were encountered: