Wednesday, September 30, 2015

a reason to hate docker

Once a quarter I perform some system maintenance on a cluster of Asterisk servers and their Dashboards. (a) backing up log and cdr files, (b) purging some logs, (d) repartitioning the cdr log database tables and the trigger that inserts the records. I happen to use Fabric as the remote execution tool. I also have a 50 line microservice that I use to create the trigger on the fly.

So far so good.

The microservice is running on a Google Compute Engine node, on CoreOS, with Docker. GCE is fine although I needed to punch a hole in the firewall. CoreOS is on release 711 or something. And docker is whatever version it is.

The nice thing is that even though this system is running well and survives reboots it has a number of major flaws. Once a quarter I need to build and run the microservice, however, it never works that way.

  • previous docker build can consume 100% of available drive space
  • I have to make sure the 9090 port is a passthru
  • have to remember how to build the container
  • and then how to run it
  • Since docker is many versions back I gotta remember the different commands as things move forward
  • documentation on the project is thin and the version control is weak
  • and the code was copied from server to server as I was resizing my servers
  • does not use a registry
This project suffers from so much technical debt! The only way to repair this is to (a) complete the project (b) remove docker (c) implement a different idea that might include launching a VPS (digital ocean is light) and doing it that way. One thing for certain... it has to be better.

No comments:

Post a Comment

dead pixels

I have never had a dead pixel so when I read: Small numbers (1-3) of stuck or dead pixels are a characteristic of LCD screens. These are n...