James Taylor jt-nti

Mistakes to Avoid: Docker Antipatterns

Whichever route you take to implementing containers, you’ll want to steer clear of common pitfalls that can undermine the efficiency of your Docker stack.

Don’t run too many processes inside a single container

The beauty of containers—and an advantage of containers over virtual machines—is that it is easy to make multiple containers interact with one another in order to compose a complete application. There is no need to run a full application inside a single container. Instead, break your application down as much as possible into discrete services, and distribute services across multiple containers. This maximizes flexibility and reliability.

Don’t install operating systems inside Docker containers

It is possible to install a complete Linux operating system inside a container. In most cases, however, this is not necessary. If your goal is to host just a single application or part of an application in the container, you need to install only the essential

Most VPN Services are Terrible

Short version: I strongly do not recommend using any of these providers. You are, of course, free to use whatever you like. My TL;DR advice: Roll your own and use Algo or Streisand. For messaging & voice, use Signal. For increased anonymity, use Tor for desktop (though recognize that doing so may actually put you at greater risk), and Onion Browser for mobile.

This mini-rant came on the heels of an interesting twitter discussion: https://twitter.com/kennwhite/status/591074055018582016

	# If you are using Windows as your Vagrant host OS, there is a limitation in Windows where any given folder path
	# cannot be more than 260 characters long. This becomes a problem with Vagrant because, for example, if you
	# install a Linux guest environment and try to create a deep directory structure in a synced folder, Linux will
	# throw errors. This is because the synced folder is under the constraints of the Windows host. A common example
	# of this happening is when installing node.js modules. NPM is known for creating some very long, deep
	# folder paths because each node depenency has it's own dependencies, which have their own dependencies, etc...
	#
	# This gist solves the problem and works around the Windows 260 character path limit. Add it to your Vagrantfile.
	#
	# NOTE: This bug in Vagrant was fixed in 1.7.3, but reverted back in 1.7.4 due to some regression bugs.

	/*
	* Basic mash up of Andrew de Quincey's Joggler light sensor code
	* and sample MQTT client code to publish light sensor reading
	* messages.
	* For more info. see:
	* http://code.google.com/p/adqmisc/source/browse/trunk/joggler/readlightsensor.c
	* http://www.eclipse.org/paho/files/mqttdoc/Cclient/
	* http://jtlog.wordpress.com/2013/02/07/mqtt-joggler/
	*/
	#include "stdio.h"