I got the same problem and fixed it creating my own dockerfile and then
adding docker binaries into that. The problem with the approach you're
following is that you need to manage all docker dependencies mounting them
to the container.
On Fri, Jan 1, 2016, 10:10 PM Klaus Ma
@ Graham, just check mesosphere/mesos-slave; it seems not include docker
binaries images; so I think you can try to mount docker binaries into this
docker image (please pay attention to dependencies), or re-build the image
yourself.
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
I did try removing the /proc and adding just pid=host but still no dice with
that. Need to have a deeper dig into the docker 1.9 changelog. Will post back
if I find anything.
Thanks,
Graham.
On 31 Dec 2015, at 20:27, Tim Chen
> wrote:
I don't
Provided that I know close to nothing about CoreOS (and very little about
docker itself) usually the 127 exit code is for a "not found" binary - are
you sure that `docker` is in the PATH of the user/process running the Mesos
agent?
Much longer shot - but worth a try: look into the permissions
4 matches
Mail list logo