Skip to main content

rancher docker registry

Earlier today I wrote an article describing a rancher quick start. When I mentioned an enterprise deployment I mentioned that I needed to install a registry server. Since docker released version 2 I thought no time like the present.

  • open the rancher console in a browser:
  • click container
  • click add container
  • provide your vanity container name: "registry". This is a name I selected not the container name in the registry
  • in the "image" select "docker" and type "registry"
  • click create
Now rancher is going go get the container and start instantiating it. I did not select the particular host but it's selected one for me. Also, rancher also started a sidekick container for the registry container so that networking is obvious.

Once the registry service is running you should add it to the rancher registry list.
  • get the IP address of the container you created above
  • click registries
  • click add registry
  • provide your vanity name for this service
  • provide the IP address
  • click add
Now if you add a new container you'll see that the registry list now includes the registry you just created.

One thing that is TBD is persisting the storage for the registry so it can be rebooted. But I did not get to that point in the configuration... but I should.

UPDATE:  I had decided to install the latest etcd. (a) adding a container seemed to be a little round robin - unexpected goodness. (b) I had to add to the registry list. (c) the first attempt to install etcd failed because I tried 'etcd' and it should have been 'coreos/etcd'. Interestingly when it failed rancher left the sidekick in running mode (with no way to delete it) and when I corrected the image name it did not create a new sidekick (assuming that rancher reused the existing). Too many unknowns.

UPDATE2: I was hoping this was the end of the story but it's not.  It seems either rancher agent or server are failing. This is not reliable for me.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…