Skip to main content

hodgepodge of Docker notes as of today

Updating the latest "box" core image for your virtualbox installation requires one quick command.
vagrant box update --box coreos-alpha
 "Yes", CoreOS will update itself based on the LockSmith settings on your system but if you are running a multinode cluster that you might be repeatedly launching and destroying... a normal vagrant box update will be processed for each node in the cluster (running or not).

I was tinkering with the latest deis source and I noticed that there were a number of patches that might have effected my experience but since the project only provides binaries of releases I would need to perform the compilation myself. The process was never completed but I did notice that their Makefile depended on boot2docker in order to deploy a working compiler environment. Being a devops build engineer I found this interesting and comforting even though it did not work properly.

Deis is a cool project. It's probably the furthest ahead of all of the Docker PaaS frameworks. Sadly it's terribly buggy, documentation is very thin, And the docs are thinest where it might matter most in the open source arena. By comparison boot2docker provides some great information for generating your own boot2docker image.

One of the big challenges with Vagrant is getting a boot partition bigger than the default 40GB. The defacto method for configuring additional drive space seems to be host mounted storage or add a virtual drive. There is nothing entirely wrong with this approach, however, boot2docker offers a default 20GB boot storage or you can resize the drive with these instructions; edit the config file here:
BOOT2DOCKER_PROFILE=~/.boot2docker/profile boot2docker init
BOOT2DOCKER_PROFILE=~/.boot2docker/profile boot2docker up
or since the latest "disksize" CLI options are not implemented yet... then use these instructions to roll you're own boot2docker-cli.

This looks like a simple way to combine fig and boot2docker. Made better with a bigger drive as I kept running out of disk space. I'm still trying to determine the best way to develop micro-services in a sandbox and then incorporate sidekicks to integrate them all.


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…