Skip to main content

Docker vs Rocket

The Docker - Rocket discussion is about to get into full swing but in fact the conversation started a long time ago and without getting into a debate on the subjective qualities of each project let's discuss the facts.

Docker is currently the leader in the Linux container market. With their acquisition of the fig project (now called machine), the implementation of the libcontainer (departing from the true LCX container), swarm for clustering containers. While the registry is open source Docker offers several SaaS solutions from free to enterprise.

CoreOS started as a bare metal OS that was meant to be immutable, much like ChromeOS, consume Docker containers as it's distributable unit of work. The CoreOS team developed etcd and fleetd to support Docker clusters. Multiple projects like Deis and Kubernetes were implemented and took advantage of the structure of CoreOS. Frankly when you have a heavy host OS & containers then you have many multiples of systems that need maintaining. CoreOS, with it's tools makes this so much easier. CoreOS also has an enterprise control program for managing the host updates.

As for Docker and Rocket... Docker is clearly encroaching on the CoreOS domain and CoreOS is responding in kind. I suppose if I were an insider I might know more about the exact timing, however, I don't think it matters much. What is interesting to me is that CoreOS is moving toward a trusted environment. This is of critical importance to me as I'm thinking about the best possible design for implementing an HSM (Host Security Module).

**Not to be confused, projectatomic is also interesting but is just enough far enough along to warrant comparison.

Only time will tell who the winner is going to be.  It should be no surprise if we come to find out that Docker's APIs and libcontainer were premeditated in order to protect their assets in a way that is opposed to the open source from which it was spawned. As for CoreOS I think they are already in the sweet spot. They are likely to be able to support both Rocket and Docker (maybe not at the same time) but until Docker deploys a proper OS or partners with someone else CoreOS will have at least one leg up.

Comments

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: http://www.eeti.com.tw/drivers_Linux.html (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 setup.sh answer all of the questio…

Prometheus vs Bosun

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

TL;DR;

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…