Skip to main content

Could the Docker bet be wrong? "The mythical man-month applied to sysadmins too."

What would happen if the Docker bet was wrong? First of all companies like VMware and OpenStack support Docker as a "me too" as far as that does. Beside rkt(Rocket) there isn't much competition. (Ubuntu has something called LXD and NixOS, Systemd, and a few other teams have wrappers around LXC. Docker is also trying to wrap itself in legal armor and it's moving from free/open to pay for play.) It's clearly all too confusing. So many companies are wrapping themselves in the multicolored robes of docker and the rest are simply hedging their pets.

Let's do a little shoestring and paper napkin analysis:

  • Docker claims to remove the duplicate features in running a proper OS per application by sharing the kernel with the host. Thus reducing the overhead and energy spent. So I ask the question: "If you're running a vannila Ubuntu in a Docker container just what is the savings? Phusion has already made certain claims about the number of daemons running and why their distros are better. Unless you are running a Scratch or possible Busybox guest you're not saving all that much compared to ESX which really does not have a host OS although it is a shim of sorts.
  • Docker security. Non existent and has a very high dependency on single source and 3rd party sourcing of dependencies and tools. It's simply nothing that can be audited. Apcera does some things right but it's too expensive and has not competition. I cannot get locked in that one trick pony.
  • Docker dumped the free boot2docker in favor of the not so free toolbox. 'nuff said.
  • While all this chroot and jail stuff is fun to play with can I really save my company money? fleet is a nice orchestration tool. Now that I have my apps written in go they port and schedule nicely. I could do more with my app and less with my containers.
  • Disaster Recover
  • lights out bootstraping
  • rkt, nspawn (said that already)
  • backups, shared volumes, hosted volumes
What am I forgetting?

Oh yeah, there are way too many sysadmins and devops that are good enough at their jobs that for all but the most seasoned paper dragons would probably rather spend their time hardening their current environment rather than rebuilding it from scratch.  The mythical man-month applied to sysadmins too.

UPDATE: if you really want to go bare metal you gotta try erlang on xen or elixir on xen. But one other advantage that I really didn't cover is that VMware and it's competition already have a class of tools that Docker is trying to attain. Trading chef, puppet, ansible orchestration for Dockerfiles or appc is ok but again why. You can do the same thing with simple perl, python and bash. Installers have been around a long time. And bootstraping too.


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…

Agile is still dead and has been since 1991

[updated 2011.09.30] yet another response to Agile is good.
When you have so much of you career invested in something like Agile, XP etc... it can be hard to see the forest for the trees. I had a consulting job in The Haag many years ago. IBM was the incumbent contractor at the customer site (a bank) but after 5 years on the job they had not written a single line of functioning code. In the office there were two teams of software people... both behind closed doors. The first team was the Data team and the second team was Functional. They rarely spoke and they never shared information. I was there for a week, introduced the client to OO and we had a functioning prototype. Smart people do smart things, You cannot make an underachiever exceptional by using Agile. Either they get "it" or they don't.
I just commented on a blog. I'm sure there is some validity to his post beyond observing that Agile Scrum is broken. It certainly is not what it was originally intended but for…

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…