example in README Failed: exit status 127

[demarant]

I tried the example shown in the README and got the following issue:

# sudo docker run --rm -v $(which docker):/usr/bin/docker:ro -v /var/run/docker.sock:/var/run/docker.sock activestate/dockron "0 * * * *" docker run ubuntu /bin/bash -c "echo Hello world"
2016/01/24 10:37:57 INFO -- Running per schedule: 0 * * * *
2016/01/24 10:38:00 INFO -- Executing: docker run ubuntu /bin/bash -c echo Hello world
2016/01/24 10:38:00 WARN -- Failed: exit status 127

I also tried to put sudo in front of the docker run command or run the dockron --privileged=true, but that also fails same way, it shouldn't be necessary though.

my docker info

# sudo docker info
Containers: 13
Images: 110
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 136
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.2.0-25-generic
Operating System: Ubuntu 15.10
CPUs: 4
Total Memory: 15.54 GiB
Name: lifebook-p702
ID: JQPE:ZHXD:GHH6:IEIP:OSOL:RHWE:DHS3:W6DJ:HEGC:B6HG:IYII:VOTZ
WARNING: No swap limit support

Did I miss something?

[MiiCode2]

$ docker info
Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 2
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 31
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 3.13.0-24-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 490.1 MiB
Name: xxxxx.xxxxx
ID: 5LPC:P5TI:C7W7:WDTB:OILZ:LW2H:OUFK:JEZL:I4Y4:QPYK:HUMU:AXRW
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
WARNING: No kernel memory limit support

If it makes you feel any better, I get the exact same error.

2016/05/26 14:22:00 INFO -- Executing: docker run ubuntu /bin/bash -c echo Hello world
2016/05/26 14:22:00 WARN -- Failed: exit status 127