Offer an alternative interface for specifying registy/repo/tag triple with docker-style syntax

[mishak87]

When listing tags of official repository results in error.

> docker-ls tags redis
ERROR: authorization rejected by registry

Listing it with library/ prefix works.

> docker-ls tags library/redis
requesting list . done
repository: library/redis
tags:
- "2"
...

Would it make sense to prepend library/ for images without <vendor>/?

[DirtyHairy]

Hi @mishak87!

Afaik, the <vendor>/<name> scheme is just a convention, and there is nothing that keeps you for creating a repo that does not have a vendor prefix (I would have to test though). Anyway, I'd rather not add any magic for resolving repository names, but I am very much inclined to add a note concerning the official registry to the documentaton.

Cheers
-Christian

[mishak87]

Yes v2 does not limit <name>.
This use-case is only when using public docker registry (aka Hub; which is default).
I think it would be more user friendly to prefix them in this case - especially for new docker users.

[DirtyHairy]

Documented in 2621ced .

[mishak87]

OT: Just a thought. Using docker/reference.WithName could simplify CLI input so registry does not have to be specified via argument. By simulating docker behaviour however it is messy would fit more into docker toolset (docker, docker-compose image names).

> docker-ls tags super.secret/vendor/project

[DirtyHairy]

Hi @mishak87 !

I'll think about it. While I think that the current interface is more clear and concise, it might be worthwhile to add a mode of operation where you specify the resource the docker way. Of course, I am also open to pull requests 😏

Cheers
-Christian