docker-run fails upon reboot

[paschdan]

in some cases the startup of docker itself is not yet finished when the docker-container should get started (upon reboot)

Then the boot.log shows something like this

 * Starting Docker daemon                                                [ OK ]
 * Stopping flush early job output to logs                               [ OK ]
 * Starting SystemD login management service                             [ OK ]
 * Starting configure virtual network devices                            [ OK ]
 * Starting Seed the pseudo random number generator on first boot        [ OK ]
 * Starting early crypto disks...                                        [ OK ]
 * Starting Bridge file events into upstart                              [ OK ]
 * Starting system logging daemon                                        [ OK ]
 * Starting Handle applying cloud-config                                 [ OK ]
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
 * Starting AppArmor profiles                                            [ OK ]
 * Stopping System V initialisation compatibility                        [ OK ]
 * Starting Seed the pseudo random number generator on first boot        [fail]
Starting docker-container:   FATA[0000] Post http:///var/run/docker.sock/v1.17/containers/create: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?

What would be the best way to come around this issue except adding a sleep in the startup script?

This is a standard ubuntu 14.04 AMI on AWS.