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

[huksley]

+1 on this. Sonatype Nexus 3 implements Docker v1, v2 APIs and does not restrict repos to [group]/[name] path.

I would like to have repos with name like
upstream/[group]/[name]

and docker-registry-frontend does not support it.

[nabbar]

+1