== For a static file-system (not an interactive registry daemon)
-- Overview For use-cases of serving docker images from a registry, that is to be read-only (pull or run, no push). It is necessary to make certain aspects of the index/registry API optional. This way the HTTP GET's made for pulling an image and layers, are provided by a basic file system server and no added logic.
Presently, there are a few custom headers that are expected of the registry, by the docker tool. If the headers are not present, then the pull of the image fails. The functionality that is using these headers ought to have some sane defaults if they are not present.
-- Example Using the attached server (though any http server like httpd or lighttpd would work too), to serve a directory. The directory fetched from http://people.gnome.org/~alexl/v1.tar.gz, looks like: