Current spec doesn't care the layout management for ref folder. Actually consumer can set up many child folder and put the reference file to any where. It seems to be a little chaos. I think it had better to build rules for this. like:
<domain>/<repository>/<reference>
domain identifies a directory.
repository identifies the image name, which may be multi-level directory, like library/ubuntu
reference identifies the image tag.
the tree looks like:
.
└── refs
└── docker.registry.io
└── library
└── ubuntu
└── latest
└── 14.04
└── busybox
└── latest
Any ref layout inconsistent to above will be regarded as illegal.
Previous comment shows that the image layout actually play as an image repository, which contains many images(as it contains manifest list). So I think the directory should be managed with multi-levels.
Current spec doesn't care the layout management for
reffolder. Actually consumer can set up many child folder and put the reference file to any where. It seems to be a little chaos. I think it had better to build rules for this. like:<domain>/<repository>/<reference>domainidentifies a directory.repositoryidentifies the image name, which may be multi-level directory, likelibrary/ubuntureferenceidentifies the image tag.the tree looks like:
Any
reflayout inconsistent to above will be regarded as illegal.Previous comment shows that the image layout actually play as an image repository, which contains many images(as it contains manifest list). So I think the directory should be managed with multi-levels.