But if the image version is changed, this would fail. Because the image is neither locally, neither the registry is available.
Kind regards, Radek Gruchalski [email protected] (mailto:[email protected]) (mailto:[email protected]) de.linkedin.com/in/radgruchalski/ (http://de.linkedin.com/in/radgruchalski/) Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. If it has come to you in error you must 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:51, haosdent wrote: > I don't think mesos log "version/tag of the image". When mesos start a docker > 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 <[email protected] > (mailto:[email protected])> wrote: > > My marathon deploy json: > > > > { > > "type": "DOCKER", > > "volumes": [ > > { > > "containerPath": "/home/myapp /log", > > "hostPath": "/home", > > "mode": "RW" > > } > > ], > > "docker": { > > "image": "docker-registry:8080/myapp:86", > > "network": "BRIDGE", > > "portMappings": [ > > { > > "containerPort": 80, > > "hostPort": 0, > > "servicePort": 80, > > "protocol": "tcp" > > } > > ], > > "privileged": false, > > "parameters": [], > > "forcePullImage": false > > } > > } > > > > > > > > From: Paul Wolfe [mailto:[email protected]] > > Sent: Tuesday, October 06, 2015 11:39 AM > > To: [email protected] (mailto:[email protected]) > > Subject: RE: Old docker version deployed > > > > No different tags. > > > > From: Rad Gruchalski [mailto:[email protected]] > > Sent: Tuesday, October 06, 2015 11:39 AM > > To: [email protected] (mailto:[email protected]) > > Subject: Re: Old docker version deployed > > > > Paul, > > > > > > > > Are you using the same tag every time? > > > > > > Kind regards, > > Radek Gruchalski > > [email protected] (mailto:[email protected]) > > (mailto:[email protected]) > > de.linkedin.com/in/radgruchalski/ (http://de.linkedin.com/in/radgruchalski/) > > > > Confidentiality: > > This communication is intended for the above-named person and may be > > confidential and/or legally privileged. > > If it has come to you in error you must 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 Wolfe <[email protected] > > > (mailto:[email protected])> wrote: > > > > Hello all, > > > > > > > > I'm new to this list, so please let me know if there is a better/more > > > > appropriate forum for this question. > > > > > > > > We are currently experimenting with marathon and mesos for deploying a > > > > simple webapp. We ship the app as a docker container. > > > > > > > > Sporadically (ie 1 out of 100) we find an old version of the app is > > > > deployed. It is obvious from the logs and the appearance of the GUI > > > > that the version is old. If I download and run the docker container > > > > locally, I see it is indeed the latest version of the code. That leads > > > > me to believe that somewhere in the marathon deploy or 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 any help! > > > > Paul Wolfe > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > The information in this e-mail is intended only for the person or > > > > entity to which it is addressed. > > > > > > > > It may contain confidential and /or privileged material. If someone > > > > other than the intended recipient should receive this e-mail, he / she > > > > shall not be entitled to read, disseminate, disclose or duplicate it. > > > > > > > > If you receive this e-mail unintentionally, please inform us > > > > immediately by "reply" and then delete it from your system. Although > > > > this information has been compiled with great care, neither IMC > > > > Financial Markets & Asset Management nor any of its related entities > > > > shall accept any responsibility for any errors, omissions or other > > > > inaccuracies in this information or for the consequences thereof, nor > > > > shall it be bound in any way by the contents of this e-mail or its > > > > attachments. In the event of incomplete or incorrect transmission, > > > > please return the e-mail to the sender and permanently delete this > > > > message and any attachments. > > > > > > > > Messages and attachments are scanned for all known viruses. Always scan > > > > attachments before opening them. > > > > > > > > > > > > -- > > > Best Regards, > > > Haosdent Huang > > > > > > > > > > > > > > > > > > > > > > > > > > > > > The information in this e-mail is intended only for the person or entity to > > which it is addressed. > > > > It may contain confidential and /or privileged material. If someone other > > than the intended recipient should receive this e-mail, he / she shall not > > be entitled to read, disseminate, disclose or duplicate it. > > > > If you receive this e-mail unintentionally, please inform us immediately by > > "reply" and then delete it from your system. Although this information has > > been compiled with great care, neither IMC Financial Markets & Asset > > Management nor any of its related entities shall accept any responsibility > > for any errors, omissions or other inaccuracies in this information or for > > the consequences thereof, nor shall it be bound in any way by the contents > > of this e-mail or its attachments. In the event of incomplete or incorrect > > transmission, please return the e-mail to the sender and permanently delete > > this message and any attachments. > > > > Messages and attachments are scanned for all known viruses. Always scan > > attachments before opening them. > > > > > > The information in this e-mail is intended only for the person or entity to > > which it is addressed. > > > > It may contain confidential and /or privileged material. If someone other > > than the intended recipient should receive this e-mail, he / she shall not > > be entitled to read, disseminate, disclose or duplicate it. > > > > If you receive this e-mail unintentionally, please inform us immediately by > > "reply" and then delete it from your system. Although this information has > > been compiled with great care, neither IMC Financial Markets & Asset > > Management nor any of its related entities shall accept any responsibility > > for any errors, omissions or other inaccuracies in this information or for > > the consequences thereof, nor shall it be bound in any way by the contents > > of this e-mail or its attachments. In the event of incomplete or incorrect > > transmission, please return the e-mail to the sender and permanently delete > > this message and any attachments. > > > > Messages and attachments are scanned for all known viruses. Always scan > > attachments before opening them. > > > > -- > Best Regards, > Haosdent Huang
