<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-virtualization.git/recipes-containers/docker-distribution/files, branch dunfell</title>
<subtitle>Mirror of git.yoctoproject.org/meta-virtualization</subtitle>
<id>https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=dunfell</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-virtualization.git/atom?h=dunfell'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/'/>
<updated>2017-03-12T05:32:33+00:00</updated>
<entry>
<title>docker-registry: provide via docker-distribution</title>
<updated>2017-03-12T05:32:33+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2017-03-12T04:37:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-virtualization.git/commit/?id=5c501c8ec8812fbf8027bc9f46ed635ff15d96e6'/>
<id>urn:sha1:5c501c8ec8812fbf8027bc9f46ed635ff15d96e6</id>
<content type='text'>
Follow the bouncing docker-registry package. Rather than use the docker hub
registry container, we can have finer grained control if we clone and build
the docker-distribution repository directly.

Since this is distinct from the main docker package/codebase, we break the
registry back out into its own package.

We also create a baseline configuration and .service file that can be the
basis for more complex implementations.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
</feed>
