Re: Failed to push sample docker image (lattice-app) to diego
Eric Malm <emalm@...>
Hi,
Does the lattice app instance stay in a down state? What happens when CF
restarts it? Also, what version of garden-linux-release is deployed?
I've just now been able to run `cf push lattice-app -o
cloudfoundry/lattice-app` to push the lattice-app image to a CF environment
running dev versions of CF and Diego later than v237 and v0.1472.0,
respectively, and according to the logs it runs fine. I observe the pair of
exit-status codes you report from the logs of this instance only when I
intentionally stop the entire app or use `cf restart-app-instance` to
restart one of its instances.
Thanks,
Eric, CF Runtime Diego PM
toggle quoted message
Show quoted text
Does the lattice app instance stay in a down state? What happens when CF
restarts it? Also, what version of garden-linux-release is deployed?
I've just now been able to run `cf push lattice-app -o
cloudfoundry/lattice-app` to push the lattice-app image to a CF environment
running dev versions of CF and Diego later than v237 and v0.1472.0,
respectively, and according to the logs it runs fine. I observe the pair of
exit-status codes you report from the logs of this instance only when I
intentionally stop the entire app or use `cf restart-app-instance` to
restart one of its instances.
Thanks,
Eric, CF Runtime Diego PM
On Sat, Jun 11, 2016 at 11:44 PM, 王小锋 <zzuwxf(a)gmail.com> wrote:
Hi, there
I uploaded my cf deployment from 233 to 237 using bosh, and deploy
diego(diego-release-0.1472.0) along cf deployoment.
The deployment itself is successful. And I am able to push apps using
buildpacks to diego backend instead of DEA backend.
Howerver, when I try to push docker image to diego backend using command:
*cf docker-push my-app cloudfoundry/lattice-app*
It failed to start , cf app my-app shows the status is down:
cf app my-app
requested state: started
instances: 0/1
usage: 1G x 1 instances
urls: my-app.example.com
last uploaded: Sun Jun 12 05:44:14 UTC 2016
stack: cflinuxfs2
buildpack: unknown
state since cpu memory disk details
#0 *down* 1970-01-01 12:00:00 AM 0.0% 0 of 1G 0 of 1G
cf docker-push my-app cloudfoundry/lattice-app
and cf logs my-app--recent shows "Lattice-app" starts successfully first,
then exit with some error. Any suggestions? Your help is appreciated!
016-06-12T05:44:14.76+0000 [API/0] OUT Created app with guid
c6c68c6b-7727-45ba-a5e9-d7a7867cc5e4
2016-06-12T05:44:15.04+0000 [API/0] OUT Updated app with guid
c6c68c6b-7727-45ba-a5e9-d7a7867cc5e4
({"route"=>"c34726a5-1275-47a4-9a49-b7a481753200"})
2016-06-12T05:44:15.68+0000 [API/0] OUT Updated app with guid
c6c68c6b-7727-45ba-a5e9-d7a7867cc5e4 ({"state"=>"STARTED"})
2016-06-12T05:44:33.95+0000 [STG/0] OUT Creating container
2016-06-12T05:44:34.19+0000 [STG/0] OUT Successfully created container
2016-06-12T05:44:34.19+0000 [STG/0] OUT Staging...
2016-06-12T05:44:34.21+0000 [STG/0] OUT Staging process started ...
2016-06-12T05:44:36.28+0000 [STG/0] OUT Staging process finished
2016-06-12T05:44:36.28+0000 [STG/0] OUT Exit status 0
2016-06-12T05:44:36.28+0000 [STG/0] OUT Staging Complete
2016-06-12T05:44:36.52+0000 [CELL/0] OUT Creating container
2016-06-12T05:44:48.13+0000 [CELL/0] OUT Successfully created container
2016-06-12T05:44:48.13+0000 [CELL/0] OUT Starting health monitoring of
container
2016-06-12T05:44:48.15+0000 [APP/0] OUT
{"timestamp":"1465710288.151398897","source":"lattice-app","message":"lattice-app.lattice-app.starting","log_level":1,"data":{"ports":["8080"]}}
2016-06-12T05:44:48.15+0000 [APP/0] OUT
{"timestamp":"1465710288.151749372","source":"lattice-app","message":"lattice-app.lattice-app.up","log_level":1,"data":{"port":"8080"}}
2016-06-12T05:44:48.65+0000 [CELL/0] OUT Container became healthy
2016-06-12T05:44:49.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:50.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:51.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:52.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:53.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:54.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:55.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:56.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:57.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:58.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:44:59.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:45:00.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:45:01.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:45:02.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:45:03.15+0000 [APP/0] OUT Lattice-app. Says Hello. on
index: 0
2016-06-12T05:45:04.09+0000 [CELL/0] OUT Exit status 0
2016-06-12T05:45:04.09+0000 [APP/0] OUT Exit status 2