-
Notifications
You must be signed in to change notification settings - Fork 173
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
[Feature request] "reg ls" should accept hostname #31
Comments
I don't think it will work on that registry just like it doesn't work for
docker hub, this is for private registries, I'm unsure of the auth protocol
for grc.io and if they implemented the entire registry api
…On Jul 10, 2017 2:12 PM, "Ahmet Alp Balkan" ***@***.***> wrote:
reg ls command should accept a registry host e.g. reg ls gcr.io,
otherwise it seems like it's randomly picking something in
.docker/config.json
$ reg ls
fRepositories for https://eu-mirror.gcr.io
^C
$ reg ls
Repositories for https://us-mirror.gcr.io
^C
$ reg ls
Repositories for https://l.gcr.io
^C
$ reg ls
Repositories for https://launcher.gcr.io
^C
$ reg ls
Repositories for https://asia.gcr.io
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#31>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABYNbKxeH4atJ4FRiy5FWgrDK1Yz4Bnzks5sMmmfgaJpZM4OTNgM>
.
|
|
@ahmetb: I get exactly the same on Codefresh (r.cfcr.io), although I have to pass a username and password manually to |
@halfer not really, due to the fact that gcr.io has not implemented the catalog API yet. |
Thanks @ahmetb - I just discovered the same on Stack Overflow! Like buses, two helpful answers come at the same time. 😺 |
reg ls
command should accept a registry host e.g.reg ls gcr.io
, otherwise it seems like it's randomly picking something in .docker/config.jsonThe text was updated successfully, but these errors were encountered: