Check if the containers are really running when starting docker
Working in progress: add unit tests for the running state check
Merge branch 'master' into 257-container_real_running_state-fix
More thorough test case, use container.Stop() instead of lxc-kill,
use setStopped() during the restore step
variable names
Better crash simulation in TestRestore ; force state lock creation when loading a container from disk
use fmt.Fprintf instead of fmt.Fprint

fmt.Fprint does not allow format strings
remove dead code in CmdPush
kill the right containers in runtime_test
use wg.Done() isntead of wg.Add(-1)
replace unreachable returns with panics

Not only is this a more common idiom, it'll make finding bugs easier,
and it'll make porting to Go 1.1 easier.

Go 1.1 will not require the final return or panic because it has a
notion of terminating statements.
remove superfluous panic
Integrated @creack's feedback on TestRestore
Moved resetLock() to the Load() method ; changed resetLock() to initLock() and changed behavior to not modify the lock if it was already set (not nil)
move each command description into a separate document
change option description to reflect the semantics

At least, for me, 'map' means that there are two values and one is "mapped" to
another.

In this case, just one value is provided (container's port), the other value is
automatically obtained (host's port) and the actual mapping can be seen using
``docker port`` command.
clean up AttachOpts type

Primarily, there is no reason to have a pointer to a map. Furthermore,
make() can be used on AttachOpts directly.
Check WaitTimeout return in test, replaced lock initialization in runtime.Register() with call to initLock()
Fix NAT problem with ports looping back to containers
Put the bridge interface name in the command line