HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
docker-archive
docker-registry
Python2013–2016
docker-archive / docker-registry · Archived

docker-registry

This is **DEPRECATED**! Please go to https://github.com/docker/distribution

Systems & InfrastructureDevOps & Cloud
Explore on GitHubRead Hacker News discussions
18Distinct people
18Mentions
0Explicit recommenders
2.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This is **DEPRECATED**! Please go to https://github.com/docker/distribution

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month18 dated mentions

Observed mentions: 2013-07-18 21:54:25 UTC to 2016-01-14 06:16:36 UTC.

0122013-07-01 00:00:00 UTC to 2013-08-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJul 20132013-08-01 00:00:00 UTC to 2013-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-01 00:00:00 UTC to 2013-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-10-01 00:00:00 UTC to 2013-11-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-11-01 00:00:00 UTC to 2013-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-01-01 00:00:00 UTC to 2014-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-02-01 00:00:00 UTC to 2014-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-03-01 00:00:00 UTC to 2014-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-04-01 00:00:00 UTC to 2014-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-05-01 00:00:00 UTC to 2014-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-06-01 00:00:00 UTC to 2014-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-07-01 00:00:00 UTC to 2014-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-08-01 00:00:00 UTC to 2014-09-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-09-01 00:00:00 UTC to 2014-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2014-10-01 00:00:00 UTC to 2014-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 20142014-11-01 00:00:00 UTC to 2014-12-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-12-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2015-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-01 00:00:00 UTC to 2015-03-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2015-03-01 00:00:00 UTC to 2015-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-04-01 00:00:00 UTC to 2015-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-05-01 00:00:00 UTC to 2015-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-06-01 00:00:00 UTC to 2015-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-01 00:00:00 UTC to 2015-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-01 00:00:00 UTC to 2015-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-01 00:00:00 UTC to 2015-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-10-01 00:00:00 UTC to 2015-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-01 00:00:00 UTC to 2015-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2016-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 2016

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 20132013-07-01 00:00:00 UTC2013-08-01 00:00:00 UTC211
Aug 20132013-08-01 00:00:00 UTC2013-09-01 00:00:00 UTC000
Sep 20132013-09-01 00:00:00 UTC2013-10-01 00:00:00 UTC000
Oct 20132013-10-01 00:00:00 UTC2013-11-01 00:00:00 UTC202
Nov 20132013-11-01 00:00:00 UTC2013-12-01 00:00:00 UTC000
Dec 20132013-12-01 00:00:00 UTC2014-01-01 00:00:00 UTC101
Jan 20142014-01-01 00:00:00 UTC2014-02-01 00:00:00 UTC000
Feb 20142014-02-01 00:00:00 UTC2014-03-01 00:00:00 UTC101
Mar 20142014-03-01 00:00:00 UTC2014-04-01 00:00:00 UTC000
Apr 20142014-04-01 00:00:00 UTC2014-05-01 00:00:00 UTC101
May 20142014-05-01 00:00:00 UTC2014-06-01 00:00:00 UTC000
Jun 20142014-06-01 00:00:00 UTC2014-07-01 00:00:00 UTC000
Jul 20142014-07-01 00:00:00 UTC2014-08-01 00:00:00 UTC000
Aug 20142014-08-01 00:00:00 UTC2014-09-01 00:00:00 UTC202
Sep 20142014-09-01 00:00:00 UTC2014-10-01 00:00:00 UTC101
Oct 20142014-10-01 00:00:00 UTC2014-11-01 00:00:00 UTC000
Nov 20142014-11-01 00:00:00 UTC2014-12-01 00:00:00 UTC202
Dec 20142014-12-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
Jan 20152015-01-01 00:00:00 UTC2015-02-01 00:00:00 UTC000
Feb 20152015-02-01 00:00:00 UTC2015-03-01 00:00:00 UTC202
Mar 20152015-03-01 00:00:00 UTC2015-04-01 00:00:00 UTC000
Apr 20152015-04-01 00:00:00 UTC2015-05-01 00:00:00 UTC101
May 20152015-05-01 00:00:00 UTC2015-06-01 00:00:00 UTC101
Jun 20152015-06-01 00:00:00 UTC2015-07-01 00:00:00 UTC000
Jul 20152015-07-01 00:00:00 UTC2015-08-01 00:00:00 UTC000
Aug 20152015-08-01 00:00:00 UTC2015-09-01 00:00:00 UTC000
Sep 20152015-09-01 00:00:00 UTC2015-10-01 00:00:00 UTC101
Oct 20152015-10-01 00:00:00 UTC2015-11-01 00:00:00 UTC000
Nov 20152015-11-01 00:00:00 UTC2015-12-01 00:00:00 UTC000
Dec 20152015-12-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
Jan 20162016-01-01 00:00:00 UTC2016-02-01 00:00:00 UTC101

What Hacker News says

18 sources
predakanga·Jan 14, 2016
There are a great many factual errors in this article and I'm sure someone will write a proper response, but I thought someone should address the most glaring: - The repeated assertion that you can only use one process container is false. As an example, the most popular non-official base image (phusion/baseimage) provides a full system including SSHd and Cron - No integration points Docker provides an extensive event stream[0], as do their tools (such as Registry[1]) - "ps, ls, find [...] are useless here" This depends on your system setup; on a standard Debian setup, all container processes are visible to the actual system. ps, top, netstat, etc will all work just fine - "You can not easily and directly access your durable non-volatile data storage" One of the most basic concepts in Docker is that of a "volume"[2]; essentially a director
Read the rest
y that bypasses Docker's abstraction layers, for performance and durability. Additionally, using your normal storage is absolutely trivial[3] - if Linux can see it, you can use it. - No authentication for images This one's true to a certain extent. While most images aren't currently signed (that's a relatively new feature[4]), it's disingenuous to say that there's no authentication at all. Docker enforces the use of HTTPS to talk to registries, and requires HTTP authentication for registry accounts. It's not signing, but it's something. Finally, just as it's a personal bugbear of mine, I would note that the userland proxy is a very real problem. It causes major issues if you need wide port ranges, spawning an instance of the proxy per port per container. There's work being done to remove it, but it can't go soon enough in my opinion. There are a great many reasons you might not want to use Docker, but a lot of what's listed on this site just doesn't check out. EDIT: Formatting [0]: https://docs.docker.com/engine/reference/api/docker_remote_a... [1]: https://github.com/docker/docker-registry/tree/master/docker... [2]: https://docs.docker.com/engine/userguide/dockervolumes/#data... [3]: https://docs.docker.com/engine/userguide/dockervolumes/#moun... [4]: https://blog.docker.com/2015/08/content-trust-docker-1-8/
In Boycott docker
ddrmanxbxfr·Sep 30, 2015
Hi, thedevopsguy. The whole goal of beluga is to take your docker-compose project from your machine to a remote host and have it running. It's meant to be used with the existing docker-machine & docker-compose tools and shouldn't interfere with any internal docker apis. Beluga was originally written in bash as we didn't want to impose runtime dependencies. Bash is usually pretty much available everywhere expect bsd. It also accounts the fact that if you have to deploy to multiple machines you won't have to rebuild your project everywhere as it can push and pull the images from either dockerhub or your own self hosted docker registry (either https://github.com/docker/docker-registry or https://github.com/docker/distribution). Here's a link to a sample node.js project that is deployed with beluga. https://github.com/cortexmedia/Beluga-Sampl
Read the rest
eProject-Nodejs It's pretty much a standard docker-machine & docker-compose project but with an additonal file.
In Show HN: Beluga 0.1 – Docker Deployment Tool
taylodl·May 28, 2015
I use a self-hosted docker registry. The good thing is the work has already been done for you! You just need to run the registry image from DockerHub. Here's the steps I used to run my registry: - Mount your storage to a local location - Pull registry image from DockerHub - docker run -p 5000:5000 -v <local storage>:<container storage> -e STORAGE_PATH=<container storage> registry - docker push registry <server>:5000/registry The last step pushes the registry image you retrieved from DockerHub into your own private registry. I'm running this registry on a VM using a Celerra share. Works like a champ! The documentation for the registry image I'm running can be found on GitHub: https://github.com/docker/docker-registry There are many storage options, you don't have to use local storage - there are several options for using cloud storage. Hop
Read the rest
e that helps!
In Ask HN: What is your docker registry setup?
shykes·Nov 5, 2014
I agree that Docker is easier to deploy than Openstack :) However... It always astounds me how some people massively over-estimate the size and influence of Docker's marketing... Why yes, of course! The way we got Google, Microsoft, Amazon and IBM to integrate it in their products is by ghost-writing PR fluff. That's also how we got 600 people to contribute 9,000+ pull requests over 18 months [1] [2] [3]. Not bad for marketing monkeys! Seriously - after seeing so many hackers work so hard to improve the project every day, the "it's all marketing fluff" crap always gets to me. It's just plain disrespectful. How much legitimate engineering work do you need to see before you start respecting other people's work? [1] https://github.com/docker/docker/pulse/monthly [2] https://github.com/docker/libcontainer/pulse/monthly [3] https://github.com/
Read the rest
docker/docker-registry/pulse/monthly
In The new hypervisor LXD
aegiso·Apr 24, 2014
First, in the real world private registries are used for builds containing source, sensitive keys, and so forth. There is a use case here. But second, no enterprisey company will use a service that bills like this, because -$4 and $250 per month all rounds down to zero, so it's not a selling point -$4 signals no support when the shit inevitably hits the fan -$4 signals this company will tank along with your data in a month An enterprise company with actual money will take an hour or two of dev time to boot up one of the open source registries (https://github.com/dotcloud/docker-registry) and stay in control. Source: working at a Docker startup for almost a year
In Show HN: Gandalf – $1 private Docker registries
ragesh·Feb 5, 2014
Yes, you can create a docker image of your product and publish it to a docker registry. Your customers can then pull the image from there and fire up containers. Docker.io doesn't offer private images yet, so you may want to run your own registry [1] if you need to restrict access. Docker doesn't let you push updates to containers. I think the best you can do is to push a new image to your registry and ask your customers to pull and fire up new containers. [1] https://github.com/dotcloud/docker-registry
In Top Startups Built on Docker
jimrhoskins·Dec 13, 2013
Yes, assuming you mean your own docker registry. Docker has open sourced https://github.com/dotcloud/docker-registry Remember the registry deals with the actual data, and delegates auth and other stuff to an index. The docker-registry has a dummy implementation of an index that has no notion of authentication or authorization, so anything you push to your private registry is really public if you don't secure it with some other method. For me, I wanted to have a real private registry with access control limited to my team. It turned out to not be too difficult to make our own registry+index implementation that is private by default. It has a basic web interface too. I've open sourced development of it https://github.com/jimrhoskins/stevedore . It's still really rough, especially on the web interface stuff, but for push/pull operations with
Read the rest
required authentication, it does the job now.
In Where are Docker images stored?
jpetazzo·Oct 17, 2013
I work for dotCloud (the company which started Docker), and I was at YaC (Yandex tech conference; the equivalent of Google I/O in Eastern Europe, if you will), and had the opportunity to discuss this with the Yandex team. Here are some extra info (that can easily be found on the web, so nothing sensitive here) - They released the Docker plugin shortly before the conference [1] - Yandex uses a distributed storage system called Elliptics [2] in many places, and they implemented an Elliptics backend for the Docker registry (the code is out there somewhere. They contributed the Elliptics backend to the Docker registry repo a couple of days ago [3]. - Cocaine is used to power various things inside Yandex, like the Yandex.Browser backend. This backend can sustain very high loads (10-100k req/s). I discussed with their Ops team, since they had s
Read the rest
pecific questions about how to identify (and remove) potential performance bottlenecks in Docker networking stack. (Good news: you can achieve native network performance within containers with zero overhead!) I'm considering writing Dockerfiles for Elliptics and Cocaine (as soon as I can find some spare time to do so...) but I would also be happy to help if other people want to do that (I'm actively monitoring the docker-user mailing list [4] so don't hesitate to get in touch through here). [1] https://github.com/cocaine/cocaine-plugins/tree/master/docke... [2] https://github.com/reverbrain/elliptics [3] https://github.com/dotcloud/docker-registry/pull/101 [4] https://groups.google.com/forum/#!forum/docker-user
In Search Engine Yandex Launches "Cocaine" To Compete With Google App Engine

Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.