Group items tagged

"The new Docker Registry 2.0 was released on April 16th, 2015. It was completely rewritten in Go with added support for the new Docker Registry HTTP API V2 (thus only working with Docker 1.6+), promising to provide faster and more secure distribution of images. If you work with Docker and for some reason decided not to use the public Docker Hub, a private Docker Registry is an essential part of your architecture. But even if you don't have private images, you will likely need to use your own registry in production/testing for efficiency. The default installation, however, runs without encryption and authentication. I was wondering what's involved in securing it. There is an official tutorial on how to configure TLS on a registry server. TLS/SSL is absolutely necessary for any secure setup, but I also wanted to enable an authentication mechanism. The Configuration Reference document describes two authentication options supported by Docker Registry itself: so-called silly and token solutions. The silly one is apparently only useful for very limited development use-cases. The token solution seems to be more serious, but because of the lack of documentation (at the time of writing), I decided to find an alternative approach to secure it. In this article I'm going to show you how to set up the Docker Registry 2.0 with username/password authentication and SSL using the official Docker Registry image and a custom configured nginx as a proxy server."

"Google Container Registry provides secure, private Docker image storage on Google Cloud Platform. While Docker provides a central registry to store public images, you may not want your images to be accessible to the world. In this case, you must use a private registry. The Google Container Registry runs on Google Cloud Platform, so can be relied upon for consistent uptime and security. The registry can be accessed through an HTTPS endpoint, so you can pull images from any machine, whether it's a Google Compute Engine instance or your own hardware."

"This is an HDFS based docker-registry."

"a pure web-based solution for browsing and modifying a private Docker registry"

Que tul? Announcing CoreOS Enterprise Registry, a secure Docker registry behind your firewall October 30, 2014 · By Joey Schorr

Security is part of everyday life. We lock our doors, protect our banking information with passwords that are usually so complicated that we tend to forget them. Using common sense to secure systems is just good practice. It's really easy to assume that because a system is internal, there is no need to enable authentication ...

"New Relic open sourced Centurion, a deployment tool for Docker used internally to run their production infrastructure. Centurion takes containers from a Docker registry and runs them on a fleet of hosts with the correct environment variables, host volume mappings, and port mappings, supporting rolling deployments out of the box."

"This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial POSH usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness. usage: see how is 'rel' used. Regarding rev, see: should 'rev' even be used. This page is also the official rel registry ([1][2]). Add new and proposed rel values to the following section: HTML5 link type extension "

"Registrator automatically register/deregisters services for Docker containers based on published ports and metadata from the container environment. Registrator supports pluggable service registries, which currently includes Consul, etcd and SkyDNS 2."

The [docker registry](https://registry.hub.docker.com/) is bursting at the seams. At the time of this writing, a search for "node" gets just under 1000 hits. How does one choose? ## What constitutes a good docker image? This is a subjective matter, but I have some criteria for a docker image that I consider good: * **working**.

"A deployment tool for Docker. Takes containers from a Docker registry and runs them on a fleet of hosts with the correct environment variables, host volume mappings, and port mappings. Supports rolling deployments out of the box, and makes it easy to ship applications to Docker servers. We're using it to run our production infrastructure."

"Automated Nginx reverse proxy for docker containers"

"This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field."

Nosotros tenemos necesidad de un repositorio de servicios, me parece que es la única manera de lograr un poco de uniformidad, claridad y exposición en cualquier esfuerzo SOA que podamos hacer en la organización. Quizás podríamos empezar un test drive de una implementación similar a lo que proponen en el artículo dado que no requiere la "elección" de un producto en particular lo cual parece ser el factor limitante en este momento "político".