docker-registry-frontend Problems handling docker images with path deeper than one directory

docker-registry-frontend cannot handle docker images added to the registry which have a deeper path than one directory. selecting a image with deeper path won't show tags, but will be redirected to the frontend home directory

{
 "repositories":
   [
   "anaconda/cijenkinsnode",
   "centos",
   "dbcompiler/ci/oraclejava",
   "dbcompiler/cijenkins",
   "dbcompiler/cijenkinsnode", 
   "dbcompiler/cioraclejava",
   "dep/jenkins/r2d2",
   "layer/dmc",
   "ci_buildenv",
   "phusion/baseimage",
   "ubuntu"
   ]
}

Examples:

images without issue:
- centos, ci_buildenv, ubuntu,
- dbcompiler/cioraclejava, phusion/baseimage ...
images whcih cannot be viewed correct in the web interface:
- dbcompiler**/ci/**oraclejava
- dep**/jenkins/**r2d2

Expected behavior is to be able to walk through the path to get the tags shown on the web page.

At the moment we are running Docker 1.12.0 on RHEL 7.2 with docker-registry-frontend:v2

Aug 17 '16 07:08 othews

@othews you're right, currently this is not supported. To cite the registry API referenc:

Classically, repository names have always been two path components where each path component is less than 30 characters. The V2 registry API does not enforce this. The rules for a repository name are as follows:

A repository name is broken up into path components. A component of a repository name must be at least one lowercase, alpha-numeric characters, optionally separated by periods, dashes or underscores. More strictly, it must match the regular expression [a-z0-9]+(?:[._-][a-z0-9]+)*.

If a repository name has two or more path components, they must be separated by a forward slash (“/”).

The total length of a repository name, including slashes, must be less the 256 characters.