-
Notifications
You must be signed in to change notification settings - Fork 172
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] Infer registry host from image name argument #32
Comments
It seems to depend on the auth being used I guess
…On Jul 10, 2017 14:27, "Ahmet Alp Balkan" ***@***.***> wrote:
In issues #30 <#30>, #31
<#31> I was mainly confused about
the way I am supposed to specify private registry host to the reg CLI.
I assumed these would work:
reg ls r.j3ss.co
reg tags r.j3ss.co/chrome
however it looks like the actual syntax is:
reg -r https://r.j3ss.co ls
reg -r https://r.j3ss.co tags chrome
To me I needed to provide full HTTPS url:
reg -d -r https://gcr.io tags ahmetb/imagename
This seemed a bit weird to me:
1. Registry host is almost always part of image name (i.e. when you
specify it while running it)
2. Docs say reg -r r.j3ss.co, but in my case all ~/.docker/config.json
starts with https://. For example docker login to docker hub creates
https://index.docker.io/v1/ which I have no idea how I can use with reg
tool.
Overall, it seems like inference of the registry host from image and being
more forgiving about URLs that appear with/without https:// prefix can
improve the user experience.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#32>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABYNbOz4uOajCcRZmUGSSLR05qgteaP4ks5sMm0LgaJpZM4OTOka>
.
|
@ahmetb if you wanna try it now it should work |
worked, thanks |
\o/
…On Mon, Jul 17, 2017 at 6:05 PM, Ahmet Alp Balkan ***@***.***> wrote:
worked, thanks
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#32 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABYNbAE5-0Ony0NqWw7-UQgVZCW_1ZLVks5sO9qzgaJpZM4OTOka>
.
--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3
pgp.mit.edu <http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In issues #30, #31 I was mainly confused about the way I am supposed to specify private registry host to the
reg
CLI.I assumed these would work:
however it looks like the actual syntax is:
To me I needed to provide full HTTPS url:
This seemed a bit weird to me:
reg -r r.j3ss.co
, but in my case all ~/.docker/config.json starts withhttps://
. For exampledocker login
to docker hub createshttps://index.docker.io/v1/
which I have no idea how I can use withreg
tool.Overall, it seems like inference of the registry host from image (if no host, default to index.docker.io) and being more forgiving about URLs that appear with/without
https://
prefix can improve the user experience.The text was updated successfully, but these errors were encountered: