RE: Old docker version deployed

ocker container, always use your image name "docker-registry:8080/myapp:86" as pull and run parameters. I think maybe some machines have problems to connect your image registry. On Tue, Oct 6, 2015 at 5:40 PM, Paul Wolfe mailto:paul.wo...@imc.nl>> wrote: My marathon

RE: Old docker version deployed

d run parameters. I think maybe some machines have problems to connect your image registry. On Tue, Oct 6, 2015 at 5:40 PM, Paul Wolfe mailto:paul.wo...@imc.nl>> wrote: My marathon deploy json: { "type": "DOCKER", "volumes": [ { "containe

RE: Old docker version deployed

er": { "image": "docker-registry:8080/myapp:86", "network": "BRIDGE", "portMappings": [ { "containerPort": 80, "hostPort": 0, "servicePort": 80, "protocol": "tcp" }

RE: Old docker version deployed

ust take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately. On Tuesday, 6 October 2015 at 11:37, haosdent wrote: You could see the stdout/stderr of your container from mesos webui. On Tue, Oct 6, 2015 at 5:30 PM, Paul Wol

RE: Old docker version deployed

: Re: Old docker version deployed You could see the stdout/stderr of your container from mesos webui. On Tue, Oct 6, 2015 at 5:30 PM, Paul Wolfe mailto:paul.wo...@imc.nl>> wrote: Hello all, I'm new to this list, so please let me know if there is a better/more appropriate for

Old docker version deployed

r the mesos running of the image, versions are getting confused. I guess my first question is what additional information can I get from marathon or mesos logs to help diagnose? I've checked the mesos-SLAVE.* but haven't been able to garner anything interesting there. Thanks for