I had a problem like this on a couple of CC100s and fixed it by doing a quick and dirty SLEEP workaround in the docker startup script. I think docker ends up in a limbo mode if the boot isn’t clean and everything else on the CC100 tries to start up at the same time.
I modified /etc/rc.d/S99_docker
and added sleep 180
before it starts the daemon.
function do_docker_start()
{
echo "configuring network..."
firewall_hook_activate
echo -n "starting docker daemon..."
sleep 180
start-stop-daemon -S --background --quiet --oknodo --pidfile $DOCKER_PIDFILE --exec /usr/bin/env PATH="/"$DOCKER_IPTABLES_PATH":$PATH" /usr/bin/dockerd -- #manipulate iptables-binary path!
}
After this I’ve never experienced the same problem again. The 180 seconds is just a random number I selected to be sure that everything else is done starting up.