Add a bunch more content

Most of these are just synced down from what the Hub already has, but some of these I've updated here.

centos/README-short.txt

@@ -1,2 +1 @@
 The official build of CentOS.
-

cirros/README-short.txt

@@ -0,0 +1 @@
+CirrOS is a Tiny OS that specializes in running on a cloud.

cirros/README.md

@@ -0,0 +1,33 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`latest`, `0.3.0` (*Dockerfile*)](https://github.com/ewindisch/docker-cirros/blob/1cded459668e8b9dbf4ef976c94c05add9bbd8e9/Dockerfile)
+
+# What is CirrOS?
+
+CirrOS is a Tiny OS that specializes in running on a cloud.
+
+> [launchpad.net/cirros](https://launchpad.net/cirros)
+
+![logo](https://raw.githubusercontent.com/docker-library/docs/master/cirros/logo.png)
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/ewindisch/docker-cirros/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/ewindisch/docker-cirros/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

cirros/content.md

@@ -0,0 +1,7 @@
+# What is CirrOS?
+
+CirrOS is a Tiny OS that specializes in running on a cloud.
+
+> [launchpad.net/cirros](https://launchpad.net/cirros)
+
+%%LOGO%%

crux/README-short.txt

@@ -0,0 +1 @@
+CRUX is a lightweight Linux distribution targeted at experienced Linux users

crux/README.md

@@ -0,0 +1,62 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`latest`, `3.0` (*Dockerfile*)](https://github.com/therealprologic/docker-crux/blob/9ed6ecae582c58138cbb0c1f95eaa5c620f0fc7e/Dockerfile)
+
+# What is CRUX?
+
+CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at
+experienced Linux users. The primary focus of this distribution is "keep it
+simple", which it reflects in a simple tar.gz-based package system, BSD-style
+initscripts, and a relatively small collection of trimmed packages. The
+secondary focus is utilization of new Linux features and recent tools and
+libraries. CRUX also has a ports system which makes it easy to install and
+upgrade applications.
+
+# Why use CRUX?
+
+There are many Linux distributions out there these days, so what makes CRUX any
+better than the others? The choice of distribution is a matter of taste, really.
+Here are a few hints about the tastes and goals of the people behind CRUX. CRUX
+is made with simplicity in mind from beginning to end.
+
+Making it easy to create new and update old packages is essential; updating a
+package in CRUX is often just a matter of typing `pkgmk -d -u`. The usage of
+ports helps keep your packages up-to-date; not the latest bleeding-edge-alpha
+version, but the latest stable version. Other features include creating packages
+optimized for your processor, eg. by compiling with `-march=x86-64`, and
+avoiding cluttering the filesystem with files you'll never use, eg.
+`/usr/doc/*`, etc. If you need more information about a specific program, other
+than information found in the man-page, Google usually knows all about it.
+
+Finally, it strives to use new features as they become available, as long as
+they are consistent with the rest of the goals. In short, CRUX might suit you
+very well if you are:
+
+* A somewhat experienced Linux user who wants a clean and solid Linux
+  distribution as the foundation of your installation.
+* A person who prefers editing configuration files with an editor to using a
+  GUI.
+* Someone who does not hesitate to download and compile programs from the
+  source.
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/therealprologic/docker-crux/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/therealprologic/docker-crux/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

crux/content.md

@@ -0,0 +1,36 @@
+# What is CRUX?
+
+CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at
+experienced Linux users. The primary focus of this distribution is "keep it
+simple", which it reflects in a simple tar.gz-based package system, BSD-style
+initscripts, and a relatively small collection of trimmed packages. The
+secondary focus is utilization of new Linux features and recent tools and
+libraries. CRUX also has a ports system which makes it easy to install and
+upgrade applications.
+
+# Why use CRUX?
+
+There are many Linux distributions out there these days, so what makes CRUX any
+better than the others? The choice of distribution is a matter of taste, really.
+Here are a few hints about the tastes and goals of the people behind CRUX. CRUX
+is made with simplicity in mind from beginning to end.
+
+Making it easy to create new and update old packages is essential; updating a
+package in CRUX is often just a matter of typing `pkgmk -d -u`. The usage of
+ports helps keep your packages up-to-date; not the latest bleeding-edge-alpha
+version, but the latest stable version. Other features include creating packages
+optimized for your processor, eg. by compiling with `-march=x86-64`, and
+avoiding cluttering the filesystem with files you'll never use, eg.
+`/usr/doc/*`, etc. If you need more information about a specific program, other
+than information found in the man-page, Google usually knows all about it.
+
+Finally, it strives to use new features as they become available, as long as
+they are consistent with the rest of the goals. In short, CRUX might suit you
+very well if you are:
+
+* A somewhat experienced Linux user who wants a clean and solid Linux
+  distribution as the foundation of your installation.
+* A person who prefers editing configuration files with an editor to using a
+  GUI.
+* Someone who does not hesitate to download and compile programs from the
+  source.

debian/README-short.txt

@@ -0,0 +1 @@
+(Semi) Official Debian base image.

debian/README.md

@@ -0,0 +1,68 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`jessie` (*jessie/Dockerfile*)](https://github.com/tianon/docker-brew-debian/blob/c126f932c08746c6be9b287d2f16d1257b6187ec/jessie/Dockerfile)
+- [`oldstable` (*oldstable/Dockerfile*)](https://github.com/tianon/docker-brew-debian/blob/c126f932c08746c6be9b287d2f16d1257b6187ec/oldstable/Dockerfile)
+- [`sid` (*sid/Dockerfile*)](https://github.com/tianon/docker-brew-debian/blob/c126f932c08746c6be9b287d2f16d1257b6187ec/sid/Dockerfile)
+- [`6.0.10`, `6.0`, `6`, `squeeze` (*squeeze/Dockerfile*)](https://github.com/tianon/docker-brew-debian/blob/c126f932c08746c6be9b287d2f16d1257b6187ec/squeeze/Dockerfile)
+- [`stable` (*stable/Dockerfile*)](https://github.com/tianon/docker-brew-debian/blob/c126f932c08746c6be9b287d2f16d1257b6187ec/stable/Dockerfile)
+- [`testing` (*testing/Dockerfile*)](https://github.com/tianon/docker-brew-debian/blob/c126f932c08746c6be9b287d2f16d1257b6187ec/testing/Dockerfile)
+- [`unstable` (*unstable/Dockerfile*)](https://github.com/tianon/docker-brew-debian/blob/c126f932c08746c6be9b287d2f16d1257b6187ec/unstable/Dockerfile)
+- [`7.6`, `7`, `wheezy`, `latest` (*wheezy/Dockerfile*)](https://github.com/tianon/docker-brew-debian/blob/c126f932c08746c6be9b287d2f16d1257b6187ec/wheezy/Dockerfile)
+- [`rc-buggy` (*debian/rc-buggy/Dockerfile*)](https://github.com/tianon/dockerfiles/blob/8c304e884f4b5b418dfdae524099ca6081a9c09a/debian/rc-buggy/Dockerfile)
+- [`experimental` (*debian/experimental/Dockerfile*)](https://github.com/tianon/dockerfiles/blob/8c304e884f4b5b418dfdae524099ca6081a9c09a/debian/experimental/Dockerfile)
+
+# What is Debian?
+
+Debian is an operating system which is composed primarily of free and
+open-source software, most of which is under the GNU General Public License, and
+developed by a group of individuals known as the Debian project. Debian is one
+of the most popular Linux distributions for personal computers and network
+servers, and has been used as a base for several other Linux distributions.
+
+> [wikipedia.org/wiki/Debian](https://en.wikipedia.org/wiki/Debian)
+
+![logo](https://raw.githubusercontent.com/docker-library/docs/master/debian/logo.png)
+
+# About this image
+
+The `debian:latest` tag will always point the latest stable release (which is,
+at the time of this writing, `debian:wheezy`).  Stable releases are also tagged
+with their version (ie, `debian:wheezy` is currently also the same as
+`debian:7.4`).
+
+The rolling tags (`debian:stable`, `debian:testing`, etc) use the rolling suite
+names in their `/etc/apt/sources.list` file (ie, `deb
+http://http.debian.net/debian testing main`).
+
+## sources.list
+
+The mirror of choice for these images is
+[http.debian.net](http://http.debian.net) so that it's as close to optimal for
+everyone as possible, regardless of location.
+
+    $ docker run debian:wheezy cat /etc/apt/sources.list
+    deb http://http.debian.net/debian wheezy main
+    deb http://http.debian.net/debian wheezy-updates main
+    deb http://security.debian.org/ wheezy/updates main
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/tianon/docker-brew-debian/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/tianon/docker-brew-debian/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

debian/content.md

@@ -0,0 +1,33 @@
+# What is Debian?
+
+Debian is an operating system which is composed primarily of free and
+open-source software, most of which is under the GNU General Public License, and
+developed by a group of individuals known as the Debian project. Debian is one
+of the most popular Linux distributions for personal computers and network
+servers, and has been used as a base for several other Linux distributions.
+
+> [wikipedia.org/wiki/Debian](https://en.wikipedia.org/wiki/Debian)
+
+%%LOGO%%
+
+# About this image
+
+The `debian:latest` tag will always point the latest stable release (which is,
+at the time of this writing, `debian:wheezy`).  Stable releases are also tagged
+with their version (ie, `debian:wheezy` is currently also the same as
+`debian:7.4`).
+
+The rolling tags (`debian:stable`, `debian:testing`, etc) use the rolling suite
+names in their `/etc/apt/sources.list` file (ie, `deb
+http://http.debian.net/debian testing main`).
+
+## sources.list
+
+The mirror of choice for these images is
+[http.debian.net](http://http.debian.net) so that it's as close to optimal for
+everyone as possible, regardless of location.
+
+    $ docker run debian:wheezy cat /etc/apt/sources.list
+    deb http://http.debian.net/debian wheezy main
+    deb http://http.debian.net/debian wheezy-updates main
+    deb http://security.debian.org/ wheezy/updates main

docker-dev/README-short.txt

@@ -0,0 +1 @@
+Docker is an open source project to pack, ship and run any application as a lightweight container

docker-dev/README.md

@@ -0,0 +1,44 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`latest`, `v1.2.0`, `v1.2` (*Dockerfile*)](https://github.com/docker/docker/blob/v1.2.0/Dockerfile)
+- [`v1.0.1`, `v1.0` (*Dockerfile*)](https://github.com/docker/docker/blob/v1.0.1/Dockerfile)
+
+# What is Docker?
+
+Docker is an open-source project that automates the deployment of applications
+inside software containers, by providing an additional layer of abstraction and
+automation of operating system–level virtualization on Linux. Docker uses
+resource isolation features of the Linux kernel such as cgroups and kernel
+namespaces to allow independent "containers" to run within a single Linux
+instance, avoiding the overhead of starting virtual machines.
+
+> [wikipedia.org/wiki/Docker_(software)](https://en.wikipedia.org/wiki/Docker_(software))
+
+![logo](https://raw.githubusercontent.com/docker-library/docs/master/docker-dev/logo.png)
+
+# About this image
+
+This image contains the building and testing environment of the Docker project
+itself, from which the official releases are made.
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/docker/docker/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/docker/docker/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

docker-dev/content.md

@@ -0,0 +1,17 @@
+# What is Docker?
+
+Docker is an open-source project that automates the deployment of applications
+inside software containers, by providing an additional layer of abstraction and
+automation of operating system–level virtualization on Linux. Docker uses
+resource isolation features of the Linux kernel such as cgroups and kernel
+namespaces to allow independent "containers" to run within a single Linux
+instance, avoiding the overhead of starting virtual machines.
+
+> [wikipedia.org/wiki/Docker_(software)](https://en.wikipedia.org/wiki/Docker_(software))
+
+%%LOGO%%
+
+# About this image
+
+This image contains the building and testing environment of the Docker project
+itself, from which the official releases are made.

fedora/README-short.txt

@@ -1,2 +1 @@
 (Semi) Official Fedora base image.
-

hipache/README-short.txt

@@ -0,0 +1 @@
+Hipache is a distributed proxy for high volumes of http/websocket traffic to large numbers of hosts

hipache/README.md

@@ -0,0 +1,40 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`latest`, `0.3.1` (*Dockerfile*)](https://github.com/dotcloud/hipache/blob/0.3.1/Dockerfile)
+
+# What is Hipache?
+
+**Hipache** (pronounced `hɪ'pætʃɪ`) is a distributed proxy designed to route
+high volumes of http and websocket traffic to unusually large numbers of virtual
+hosts, in a highly dynamic topology where backends are added and removed several
+times per second. It is particularly well-suited for PaaS
+(platform-as-a-service) and other environments that are both business-critical
+and multi-tenant.
+
+Hipache was originally developed at [dotCloud](http://www.dotcloud.com), a
+popular platform-as-a-service, to replace its first-generation routing layer
+based on a heavily instrumented nginx deployment. It currently serves production
+traffic for tens of thousands of applications hosted on dotCloud. Hipache is
+based on the node-http-proxy library.
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/dotcloud/hipache/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/dotcloud/hipache/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

hipache/content.md

@@ -0,0 +1,14 @@
+# What is Hipache?
+
+**Hipache** (pronounced `hɪ'pætʃɪ`) is a distributed proxy designed to route
+high volumes of http and websocket traffic to unusually large numbers of virtual
+hosts, in a highly dynamic topology where backends are added and removed several
+times per second. It is particularly well-suited for PaaS
+(platform-as-a-service) and other environments that are both business-critical
+and multi-tenant.
+
+Hipache was originally developed at [dotCloud](http://www.dotcloud.com), a
+popular platform-as-a-service, to replace its first-generation routing layer
+based on a heavily instrumented nginx deployment. It currently serves production
+traffic for tens of thousands of applications hosted on dotCloud. Hipache is
+based on the node-http-proxy library.

jenkins/README-short.txt

@@ -0,0 +1 @@
+Official Jenkins Docker image

jenkins/README.md

@@ -0,0 +1,67 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`latest`, `1.565.3` (*Dockerfile*)](https://github.com/cloudbees/jenkins-ci.org-docker/blob/b2b442e360cf92317326fa4e325a81ab1f11a422/Dockerfile)
+- [`weekly`, `1.583` (*Dockerfile*)](https://github.com/cloudbees/jenkins-ci.org-docker/blob/f969422940ce4b2cd0bbbdcf31ea96fa2485e86c/Dockerfile)
+
+# Jenkins
+
+The Jenkins Continuous Integration and Delivery server.
+
+This is a fully functional Jenkins server, based on the Long Term Support
+release [http://jenkins-ci.org/](http://jenkins-ci.org/).
+
+![logo](http://jenkins-ci.org/sites/default/files/jenkins_logo.png)
+
+# How to use this image
+
+    docker run -p 8080:8080 jenkins
+
+This will store the workspace in /var/jenkins_home. All Jenkins data lives in there - including plugins and configuration. You will probably want to make that a persistent volume:
+
+    docker run --name myjenkins -p 8080:8080 -v /var/jenkins_home jenkins
+
+The volume for the "myjenkins" named container will then be persistent.
+
+You can also bind mount in a volume from the host:
+
+First, ensure that /your/home is accessible by the jenkins user in container (jenkins user - uid 102 normally - or use -u root), then:
+
+    docker run -p 8080:8080 -v /your/home:/var/jenkins_home jenkins
+
+## Backing up data
+
+If you bind mount in a volume - you can simply back up that directory (which is jenkins_home) at any time.
+
+If your volume is inside a container - you can use `docker cp $ID:/var/jenkins_home` command to extract the data.
+
+## Attaching build executors 
+
+You can run builds on the master (out of the box) buf if you want to attach build slave servers: make sure you map the port: `-p 50000:50000` - which will be used when you connect a slave agent.
+
+[Here](https://registry.hub.docker.com/u/maestrodev/build-agent/) is an example docker container you can use as a build server with lots of good tools installed - which is well worth trying.
+
+## Upgrading
+
+All the data needed is in the /var/jenkins_home directory - so depending on how you manage that - depends on how you upgrade. Generally - you can copy it out - and then "docker pull" the image again - and you will have the latest LTS - you can then start up with -v pointing to that data (/var/jenkins_home) and everything will be as you left it.
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/cloudbees/jenkins-ci.org-docker/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/cloudbees/jenkins-ci.org-docker/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

jenkins/content.md

@@ -0,0 +1,40 @@
+# Jenkins
+
+The Jenkins Continuous Integration and Delivery server.
+
+This is a fully functional Jenkins server, based on the Long Term Support
+release [http://jenkins-ci.org/](http://jenkins-ci.org/).
+
+![logo](http://jenkins-ci.org/sites/default/files/jenkins_logo.png)
+
+# How to use this image
+
+    docker run -p 8080:8080 jenkins
+
+This will store the workspace in /var/jenkins_home. All Jenkins data lives in there - including plugins and configuration. You will probably want to make that a persistent volume:
+
+    docker run --name myjenkins -p 8080:8080 -v /var/jenkins_home jenkins
+
+The volume for the "myjenkins" named container will then be persistent.
+
+You can also bind mount in a volume from the host:
+
+First, ensure that /your/home is accessible by the jenkins user in container (jenkins user - uid 102 normally - or use -u root), then:
+
+    docker run -p 8080:8080 -v /your/home:/var/jenkins_home jenkins
+
+## Backing up data
+
+If you bind mount in a volume - you can simply back up that directory (which is jenkins_home) at any time.
+
+If your volume is inside a container - you can use `docker cp $ID:/var/jenkins_home` command to extract the data.
+
+## Attaching build executors 
+
+You can run builds on the master (out of the box) buf if you want to attach build slave servers: make sure you map the port: `-p 50000:50000` - which will be used when you connect a slave agent.
+
+[Here](https://registry.hub.docker.com/u/maestrodev/build-agent/) is an example docker container you can use as a build server with lots of good tools installed - which is well worth trying.
+
+## Upgrading
+
+All the data needed is in the /var/jenkins_home directory - so depending on how you manage that - depends on how you upgrade. Generally - you can copy it out - and then "docker pull" the image again - and you will have the latest LTS - you can then start up with -v pointing to that data (/var/jenkins_home) and everything will be as you left it.

neurodebian/README-short.txt

@@ -0,0 +1 @@
+NeuroDebian provides neuroscience research software for Debian, Ubuntu, and other derivatives.

neurodebian/README.md

@@ -0,0 +1,68 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`lucid`, `nd10.04` (*dockerfiles/lucid/Dockerfile*)](https://github.com/neurodebian/dockerfiles/blob/6ee7033cb630b4a72fa3a4a56ad6046405efacdf/dockerfiles/lucid/Dockerfile)
+- [`precise`, `nd12.04` (*dockerfiles/precise/Dockerfile*)](https://github.com/neurodebian/dockerfiles/blob/6ee7033cb630b4a72fa3a4a56ad6046405efacdf/dockerfiles/precise/Dockerfile)
+- [`trusty`, `nd14.04` (*dockerfiles/trusty/Dockerfile*)](https://github.com/neurodebian/dockerfiles/blob/6ee7033cb630b4a72fa3a4a56ad6046405efacdf/dockerfiles/trusty/Dockerfile)
+- [`squeeze`, `nd60` (*dockerfiles/squeeze/Dockerfile*)](https://github.com/neurodebian/dockerfiles/blob/6ee7033cb630b4a72fa3a4a56ad6046405efacdf/dockerfiles/squeeze/Dockerfile)
+- [`wheezy`, `nd70`, `latest` (*dockerfiles/wheezy/Dockerfile*)](https://github.com/neurodebian/dockerfiles/blob/6ee7033cb630b4a72fa3a4a56ad6046405efacdf/dockerfiles/wheezy/Dockerfile)
+- [`jessie`, `nd80` (*dockerfiles/jessie/Dockerfile*)](https://github.com/neurodebian/dockerfiles/blob/6ee7033cb630b4a72fa3a4a56ad6046405efacdf/dockerfiles/jessie/Dockerfile)
+- [`sid`, `nd` (*dockerfiles/sid/Dockerfile*)](https://github.com/neurodebian/dockerfiles/blob/6ee7033cb630b4a72fa3a4a56ad6046405efacdf/dockerfiles/sid/Dockerfile)
+
+# What is NeuroDebian?
+
+NeuroDebian provides a large collection of popular neuroscience research
+software for the [Debian](http://www.debian.org) operating system as well as
+[Ubuntu](http://www.ubuntu.com) and other derivatives. Popular packages include
+*AFNI*, *FSL*, *PyMVPA*, and many others. While we do strive to maintain a high
+level of quality, we make no guarantee that a given package works as expected,
+so use them at your own risk.
+
+> [neuro.debian.net](http://neuro.debian.net/)
+
+![logo](https://raw.githubusercontent.com/docker-library/docs/master/neurodebian/logo.png)
+
+# About this image
+
+NeuroDebian images only add NeuroDebian repository and repository's GPG key. No
+apt indexes are downloaded, so `apt-get update` needs to be ran before any use
+of `apt-get`.
+
+`nd` tags are used to reflect suffixes used in versions of packages available
+from NeuroDebian.
+
+The `neurodebian:latest` tag will always point the Neurodebian-enabled latest
+stable release of Debian (which is, at the time of this writing,
+`debian:wheezy`).
+
+## sources.list
+
+NeuroDebian APT file is installed under
+`/etc/apt/sources.list.d/neurodebian.sources.list` and currently enables only
+`main` (DFSG-compliant) area of the archive:
+
+    > docker run neurodebian:latest cat /etc/apt/sources.list.d/neurodebian.sources.list
+    deb http://neuro.debian.net/debian wheezy main
+    deb http://neuro.debian.net/debian data main
+    #deb-src http://neuro.debian.net/debian-devel wheezy main
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/neurodebian/dockerfiles/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/neurodebian/dockerfiles/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

neurodebian/content.md

@@ -0,0 +1,36 @@
+# What is NeuroDebian?
+
+NeuroDebian provides a large collection of popular neuroscience research
+software for the [Debian](http://www.debian.org) operating system as well as
+[Ubuntu](http://www.ubuntu.com) and other derivatives. Popular packages include
+*AFNI*, *FSL*, *PyMVPA*, and many others. While we do strive to maintain a high
+level of quality, we make no guarantee that a given package works as expected,
+so use them at your own risk.
+
+> [neuro.debian.net](http://neuro.debian.net/)
+
+%%LOGO%%
+
+# About this image
+
+NeuroDebian images only add NeuroDebian repository and repository's GPG key. No
+apt indexes are downloaded, so `apt-get update` needs to be ran before any use
+of `apt-get`.
+
+`nd` tags are used to reflect suffixes used in versions of packages available
+from NeuroDebian.
+
+The `neurodebian:latest` tag will always point the Neurodebian-enabled latest
+stable release of Debian (which is, at the time of this writing,
+`debian:wheezy`).
+
+## sources.list
+
+NeuroDebian APT file is installed under
+`/etc/apt/sources.list.d/neurodebian.sources.list` and currently enables only
+`main` (DFSG-compliant) area of the archive:
+
+    > docker run neurodebian:latest cat /etc/apt/sources.list.d/neurodebian.sources.list
+    deb http://neuro.debian.net/debian wheezy main
+    deb http://neuro.debian.net/debian data main
+    #deb-src http://neuro.debian.net/debian-devel wheezy main

node/README.md

@@ -1,11 +1,14 @@
 # Supported tags and respective `Dockerfile` links
 
-- [`0.10.32`, `0.10`, `0`, `latest` (*0.10/Dockerfile*)](https://github.com/docker-library/node/blob/495f43c34ba06ed9fffa1ac59a763ac450b52ee1/0.10/Dockerfile)
+- [`0.10.32`, `0.10`, `0`, `latest` (*0.10/Dockerfile*)](https://github.com/docker-library/node/blob/824c3161f9a7fa393cb60582edbbd713a0d08ceb/0.10/Dockerfile)
 - [`0.10.32-onbuild`, `0.10-onbuild`, `0-onbuild`, `onbuild` (*0.10/onbuild/Dockerfile*)](https://github.com/docker-library/node/blob/ac05e7f96c477223f0d2da1817e84403363a65e8/0.10/onbuild/Dockerfile)
-- [`0.11.14`, `0.11` (*0.11/Dockerfile*)](https://github.com/docker-library/node/blob/495f43c34ba06ed9fffa1ac59a763ac450b52ee1/0.11/Dockerfile)
+- [`0.10.32-slim`, `0.10-slim`, `0-slim`, `slim` (*0.10/slim/Dockerfile*)](https://github.com/docker-library/node/blob/824c3161f9a7fa393cb60582edbbd713a0d08ceb/0.10/slim/Dockerfile)
+- [`0.11.14`, `0.11` (*0.11/Dockerfile*)](https://github.com/docker-library/node/blob/824c3161f9a7fa393cb60582edbbd713a0d08ceb/0.11/Dockerfile)
 - [`0.11.14-onbuild`, `0.11-onbuild` (*0.11/onbuild/Dockerfile*)](https://github.com/docker-library/node/blob/ac05e7f96c477223f0d2da1817e84403363a65e8/0.11/onbuild/Dockerfile)
-- [`0.8.28`, `0.8` (*0.8/Dockerfile*)](https://github.com/docker-library/node/blob/4acda49c86a7e024c29f882a6d7f4bbc6c2e412c/0.8/Dockerfile)
+- [`0.11.14-slim`, `0.11-slim` (*0.11/slim/Dockerfile*)](https://github.com/docker-library/node/blob/824c3161f9a7fa393cb60582edbbd713a0d08ceb/0.11/slim/Dockerfile)
+- [`0.8.28`, `0.8` (*0.8/Dockerfile*)](https://github.com/docker-library/node/blob/824c3161f9a7fa393cb60582edbbd713a0d08ceb/0.8/Dockerfile)
 - [`0.8.28-onbuild`, `0.8-onbuild` (*0.8/onbuild/Dockerfile*)](https://github.com/docker-library/node/blob/ac05e7f96c477223f0d2da1817e84403363a65e8/0.8/onbuild/Dockerfile)
+- [`0.8.28-slim`, `0.8-slim` (*0.8/slim/Dockerfile*)](https://github.com/docker-library/node/blob/824c3161f9a7fa393cb60582edbbd713a0d08ceb/0.8/slim/Dockerfile)
 
 # What is Node.js?
 

opensuse/README-short.txt

@@ -0,0 +1 @@
+This project contains the stable releases of the openSUSE distribution.

opensuse/README.md

@@ -0,0 +1,52 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`latest`, `13.1`, `bottle` (*docker/Dockerfile*)](https://github.com/openSUSE/docker-containers-build/blob/fc6453ff4ce5d67ed77aad572acbf311214b41dc/docker/Dockerfile)
+
+# openSUSE
+
+This project contains the stable releases of the openSUSE distribution.
+
+# Naming conventions
+
+Each image is tagged using both the release number (eg *"13.1"*) and the code
+name (eg *"Bottle"*). The latest stable release is always available using the
+"*latest*" tag.
+
+# Building
+
+These images are generated using [KIWI](https://github.com/openSUSE/kiwi). Their
+source file can be found on [this
+repository](https://github.com/openSUSE/docker-containers).
+
+# Repositories and packages
+
+The package selection is kept minimal to reduce the footprint of the image.
+
+However the following repositories are already part of the image:
+
+  * OSS
+  * OSS Updates
+  * Non-OSS
+  * Non-OSS Updates
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/openSUSE/docker-containers-build/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/openSUSE/docker-containers-build/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

opensuse/content.md

@@ -0,0 +1,26 @@
+# openSUSE
+
+This project contains the stable releases of the openSUSE distribution.
+
+# Naming conventions
+
+Each image is tagged using both the release number (eg *"13.1"*) and the code
+name (eg *"Bottle"*). The latest stable release is always available using the
+"*latest*" tag.
+
+# Building
+
+These images are generated using [KIWI](https://github.com/openSUSE/kiwi). Their
+source file can be found on [this
+repository](https://github.com/openSUSE/docker-containers).
+
+# Repositories and packages
+
+The package selection is kept minimal to reduce the footprint of the image.
+
+However the following repositories are already part of the image:
+
+  * OSS
+  * OSS Updates
+  * Non-OSS
+  * Non-OSS Updates

redis/README.md

@@ -56,7 +56,7 @@ You can create your own Dockerfile that adds a redis.conf from the context into
 
 Alternatively, you can specify something along the same lines with `docker run` options.
 
-    ocker run --volumes-from datacontainer --name myredis redis
+    docker run --volumes-from datacontainer --name myredis redis
 
 Using this method means that there is no need for you to have a Dockerfile for your redis container.
 

redis/content.md

@@ -40,6 +40,6 @@ You can create your own Dockerfile that adds a redis.conf from the context into
 
 Alternatively, you can specify something along the same lines with `docker run` options.
 
-    ocker run --volumes-from datacontainer --name myredis redis
+    docker run --volumes-from datacontainer --name myredis redis
 
 Using this method means that there is no need for you to have a Dockerfile for your redis container.

registry/README-short.txt

@@ -0,0 +1 @@
+Containerized docker registry

registry/README.md

@@ -0,0 +1,57 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`latest`, `0.8.1` (*Dockerfile*)](https://github.com/docker/docker-registry/blob/0.8.1/Dockerfile)
+- [`0.6.9` (*Dockerfile*)](https://github.com/docker/docker-registry/blob/0.6.9-fixed/Dockerfile)
+- [`0.7.3` (*Dockerfile*)](https://github.com/docker/docker-registry/blob/0.7.3/Dockerfile)
+
+# Docker Registry
+
+See comprehensive documentation on our [GitHub
+page](https://github.com/docker/docker-registry).
+
+## Run the Registry
+
+### Recommended: run the registry docker container
+
+ * install docker according to the [following
+   instructions](http://docs.docker.io/installation/#installation)
+ * run the registry: `docker run -p 5000:5000 registry`
+
+or
+
+```
+docker run \
+         -e SETTINGS_FLAVOR=s3 \
+         -e AWS_BUCKET=acme-docker \
+         -e STORAGE_PATH=/registry \
+         -e AWS_KEY=AKIAHSHB43HS3J92MXZ \
+         -e AWS_SECRET=xdDowwlK7TJajV1Y7EoOZrmuPEJlHYcNP2k4j49T \
+         -e SEARCH_BACKEND=sqlalchemy \
+         -p 5000:5000 \
+         registry
+```
+
+NOTE: The container will try to allocate the port 5000. If the port is already
+taken, find out which container is already using it by running `docker ps`.
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/docker/docker-registry/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/docker/docker-registry/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

registry/content.md

@@ -0,0 +1,29 @@
+# Docker Registry
+
+See comprehensive documentation on our [GitHub
+page](https://github.com/docker/docker-registry).
+
+## Run the Registry
+
+### Recommended: run the registry docker container
+
+ * install docker according to the [following
+   instructions](http://docs.docker.io/installation/#installation)
+ * run the registry: `docker run -p 5000:5000 registry`
+
+or
+
+```
+docker run \
+         -e SETTINGS_FLAVOR=s3 \
+         -e AWS_BUCKET=acme-docker \
+         -e STORAGE_PATH=/registry \
+         -e AWS_KEY=AKIAHSHB43HS3J92MXZ \
+         -e AWS_SECRET=xdDowwlK7TJajV1Y7EoOZrmuPEJlHYcNP2k4j49T \
+         -e SEARCH_BACKEND=sqlalchemy \
+         -p 5000:5000 \
+         registry
+```
+
+NOTE: The container will try to allocate the port 5000. If the port is already
+taken, find out which container is already using it by running `docker ps`.

scratch/README-short.txt

@@ -0,0 +1 @@
+an explicitly empty image, especially for building images "FROM scratch"

scratch/README.md

@@ -0,0 +1,5 @@
+# `FROM scratch`
+
+This image is most useful in the context of building base images or super
+minimal images (such as images that contain only a single binary; see
+[`hello-world`](https://github.com/docker-library/hello-world) for an example).

ubuntu-debootstrap/README-short.txt

@@ -0,0 +1 @@
+debootstrap --variant=minbase --components=main,universe --include=inetutils-ping,iproute2 <suite> /

ubuntu-debootstrap/README.md

@@ -0,0 +1,37 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`10.04.4`, `10.04`, `lucid` (*10.04/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-debootstrap/blob/b8758eac0f9c23c3b81e475c8b79ce8b469429df/10.04/Dockerfile)
+- [`12.04.5`, `12.04`, `precise` (*12.04/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-debootstrap/blob/b8758eac0f9c23c3b81e475c8b79ce8b469429df/12.04/Dockerfile)
+- [`14.04.1`, `14.04`, `trusty`, `latest` (*14.04/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-debootstrap/blob/b8758eac0f9c23c3b81e475c8b79ce8b469429df/14.04/Dockerfile)
+- [`14.10`, `utopic` (*14.10/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-debootstrap/blob/b8758eac0f9c23c3b81e475c8b79ce8b469429df/14.10/Dockerfile)
+- [`devel` (*devel/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-debootstrap/blob/b8758eac0f9c23c3b81e475c8b79ce8b469429df/devel/Dockerfile)
+
+# `ubuntu-debootstrap`
+
+This image is the result of running `debootstrap --variant=minbase` against the
+currently supported suites of the Ubuntu distribution.  It is not official or
+supported by Canonical in any way.  For an official Ubuntu image that is
+supported by Canonical, see
+[`ubuntu`](https://registry.hub.docker.com/_/ubuntu/).
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/tianon/docker-brew-ubuntu-debootstrap/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/tianon/docker-brew-ubuntu-debootstrap/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

ubuntu-debootstrap/content.md

@@ -0,0 +1,7 @@
+# `ubuntu-debootstrap`
+
+This image is the result of running `debootstrap --variant=minbase` against the
+currently supported suites of the Ubuntu distribution.  It is not official or
+supported by Canonical in any way.  For an official Ubuntu image that is
+supported by Canonical, see
+[`ubuntu`](https://registry.hub.docker.com/_/ubuntu/).

ubuntu-upstart/README-short.txt

@@ -0,0 +1 @@
+Upstart is an event-based replacement for the /sbin/init daemon which starts processes at boot

ubuntu-upstart/README.md

@@ -0,0 +1,38 @@
+# Supported tags and respective `Dockerfile` links
+
+- [`12.04`, `precise` (*sbin-init/ubuntu/upstart/12.04/Dockerfile*)](https://github.com/tianon/dockerfiles/blob/4d24a12b54b75b3e0904d8a285900d88d3326361/sbin-init/ubuntu/upstart/12.04/Dockerfile)
+- [`14.04`, `trusty`, `latest` (*sbin-init/ubuntu/upstart/14.04/Dockerfile*)](https://github.com/tianon/dockerfiles/blob/4d24a12b54b75b3e0904d8a285900d88d3326361/sbin-init/ubuntu/upstart/14.04/Dockerfile)
+- [`14.10`, `utopic` (*sbin-init/ubuntu/upstart/14.10/Dockerfile*)](https://github.com/tianon/dockerfiles/blob/4d24a12b54b75b3e0904d8a285900d88d3326361/sbin-init/ubuntu/upstart/14.10/Dockerfile)
+
+# What is Upstart?
+
+Upstart is an event-based replacement for the traditional init daemon – the
+method by which several Unix-like computer operating systems perform tasks when
+the computer is started. It was written by Scott James Remnant, a former
+employee of Canonical Ltd.
+
+> [wikipedia.org/wiki/Upstart](https://en.wikipedia.org/wiki/Upstart)
+
+![logo](https://raw.githubusercontent.com/docker-library/docs/master/ubuntu-upstart/logo.png)
+
+# User Feedback
+
+## Issues
+
+If you have any problems with or questions about this image, please contact us
+ through a [GitHub issue](https://github.com/tianon/dockerfiles/issues).
+
+You can also reach many of the official image maintainers via the
+`#docker-library` IRC channel on [Freenode](https://freenode.net).
+
+## Contributing
+
+You are invited to contribute new features, fixes, or updates, large or small;
+we are always thrilled to receive pull requests, and do our best to process them
+as fast as we can.
+
+Before you start to code, we recommend discussing your plans 
+through a [GitHub issue](https://github.com/tianon/dockerfiles/issues), especially for more ambitious
+contributions. This gives other contributors a chance to point you in the right
+direction, give you feedback on your design, and help you find out if someone
+else is working on the same thing.

ubuntu-upstart/content.md

@@ -0,0 +1,10 @@
+# What is Upstart?
+
+Upstart is an event-based replacement for the traditional init daemon – the
+method by which several Unix-like computer operating systems perform tasks when
+the computer is started. It was written by Scott James Remnant, a former
+employee of Canonical Ltd.
+
+> [wikipedia.org/wiki/Upstart](https://en.wikipedia.org/wiki/Upstart)
+
+%%LOGO%%

ubuntu/README.md

@@ -1,8 +1,8 @@
 # Supported tags and respective `Dockerfile` links
 
-- [`12.04.5`, `12.04`, `precise` (*precise/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-core/blob/2b105575647a7e2030ff344d427c3920b89e17a9/precise/Dockerfile)
-- [`14.04.1`, `14.04`, `trusty`, `latest` (*trusty/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-core/blob/2b105575647a7e2030ff344d427c3920b89e17a9/trusty/Dockerfile)
-- [`14.10`, `utopic` (*utopic/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-core/blob/2b105575647a7e2030ff344d427c3920b89e17a9/utopic/Dockerfile)
+- [`12.04.5`, `12.04`, `precise` (*precise/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-core/blob/ec15aea17b31eda47dc22f0c6ebbfebbe6094c1f/precise/Dockerfile)
+- [`14.04.1`, `14.04`, `trusty`, `latest` (*trusty/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-core/blob/ec15aea17b31eda47dc22f0c6ebbfebbe6094c1f/trusty/Dockerfile)
+- [`14.10`, `utopic` (*utopic/Dockerfile*)](https://github.com/tianon/docker-brew-ubuntu-core/blob/ec15aea17b31eda47dc22f0c6ebbfebbe6094c1f/utopic/Dockerfile)
 
 # Ubuntu