Skip to main content

Choosing the right host for your docker containers

First of all there are a lot of choices, however, they come in two varieties. The first is and probably the most common is the general purpose Linux distribution. So long as you have a modern kernel with the requisite kernel modules Docker is likely to work. (FreeBSD's compatibility mode is an API layer and not a kernel virtualization). The second type of host is the special purpose or dedicated host.

To put it plainly the general purpose Linux distro is best utilized as development environment so long as all of the other components are present depending on your production environment. ie if you have a dependency on etcd or geard etc...

On the other hand the dedicated distros work equally as well as a production environment and development environment (without the desktop). Here is a list of the hosts.
  • CoreOS - supports both Docker and Rocket
  • ProjectAtomic (Fedora, CentOS, RedHat flavors)
  • Ubuntu 'Snappy Core' - I'm not sure of that's a project name or the brand.
  • Boot2docker - more of a development environment for Windows and OSX users
The Docker and CoreOS teams have been trading quips lately. In the end I have no idea exactly what's going to happen. Both teams have great ideas and their execution is enviable. Where I struggle is if Rocket succeeds and grabs a big enough market share that currently they are alone as a host provider. If Docker continues it's momentum will they ever reach a level of stability that it becomes low risk enough without having to fork an API layer? And will they ever encroach into the host OS market? (CoreOS is awesome in that space).

At this point it might come down to the orchestration and scheduling systems like:
and others. (maybe even home grown). What interesting here is that there are several VPS offerings that are just containers. This in itself is curious. Just look at joynet.

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…