safety, about to start porting tests
updating test to correctly handle new build style
got original tests passing with the new rules for build
first passing extract test
got second test passing on extract
removed spurious prints
fixed based on new version of docker client
Using kingpin for saner cmd line arguments / flag parsing.

Provides a better documentation as well.
Fix outdated comment in Release.sh

After 8fe826fbb73b6c29e00e38440fa9aea422e502b9, we build on multiple
architectures; this updates the comment to match.
Added etcdget and etcdset actions thatw ill help with sharing state.

Either cross container state
or state from outside, for example ftest might want to retrive IP's,
nodeids and such.
Storing contianers IP's and exposed ports in etcd. added that info to "pickett ps"
tweak
Fixes to etcd commands
pickett etcd
Add short names to debug and configFile parameters.
make Byron comfy
remove trueMain (it's not being called)
Don't require the VBoxManage tool if we're not going to do path translation.

In the future, perhaps we should rename the VirtualBox interface to something
more general -- PathTranslator? -- then have a no-op implementation as well as a
VBoxManage implementation.
Trim leading slashes off of container names we get from `docker inspect`.

Do so immediately after getting the slash-prepended name from Docker, rather
than ad-hoc later on.

For reasons I don't fully understand, un-normalized container lookups (GET
/containers//foo_bar/json) were failing when made over a unix socket, rather
than a TCP connection.  Maybe go-dockerclient is wiring up the HTTP client in a
way that does path normalization over TCP but not unix sockets?
Rip out dependency on virtualbox

We still do path translation when DOCKER_HOST is tcp://, but always use the home
directory guessing logic rather than try to determine where vagrant has mounted
things.  @iansmith tells me that we were always taking this codepath before,
because vboxmanage doesn't report useful information on NFS shares.