Skip to content

Conversation

@FrontSide
Copy link

If an image has the same name as a top level repository, the user got thrown back to the landing page and was thus not able to see the tags of this image. This fixes this issue for me.

For example:
A image stored on the registry at:
private.registry.com:5000/redis

is displayed on the frontend as follows:
Redis Image

Clicking this link currently doesn't show the user the image's tags but instead throws the user back to the landing page.

David Rieger and others added 2 commits February 2, 2016 17:14
… thrown back to the landing page and was thus not able to see the tags of this image. This commit fixes this issue.
@Morriz
Copy link

Morriz commented Mar 28, 2016

If this works and has no side effects, can it be merged? I am maintaining a fork based on this fix, but don't wish to just for that ;)

@FrontSide FrontSide force-pushed the v2 branch 3 times, most recently from 086f9ee to 627f99b Compare April 11, 2016 13:51
After the tag detail change has been merged in, the changes made
before to support accessing repositories that have tha same name as user
are not sufficeient anymore.

With these chages it is now possible to list the detail tag page of all
repositories.
This variable will be used to display the hostname of the docker registry
on the tag detail page for the docker pull command.

Since as actual host, usually, the docker container 'registry'
is defined, 'registry' would also show up in this command
even though it's not the actual URL to the docker-registry
from which the image can be pulled.
@FrontSide
Copy link
Author

Not up to date anymore. Close.
My fork, however, supports this feature (also after the details addition).

@FrontSide FrontSide closed this Apr 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants