Re: [google-appengine] Re: Google Cloud Run Container Status

2020-05-08 Thread 'David (Cloud Platform Support)' via Google App Engine
You mentioned you tried delaying port binding and it did not work, can you explain what happens exactly? As Cloud Run should start sending traffic to your application once you start listening on the port number so if you are delaying the port binding, it should work in your benefit. -- You

Re: [google-appengine] Re: Google Cloud Run Container Status

2020-05-07 Thread Rodrigo Silveira
What I'm trying to accomplish is to have Cloud Run not drive traffic to my container until it's fully loaded. I have Docker health checks that do that, but Cloud Run seems to ignore them. I also delay the port binding (as suggested by Jason Collins), but again, Cloud Run seems to ignore that as

[google-appengine] Re: Google Cloud Run Container Status

2020-05-07 Thread 'Elliott (Cloud Platform Support)' via Google App Engine
Hello Rodrigo, What do you have in mind to optimize on the Docker side? Although this may not be the right forum for that, maybe we can help. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop

[google-appengine] Re: Google Cloud Run Container Status

2020-05-05 Thread Rodrigo Silveira
Update: after posting the above and stating that I'd optimized everything that could be optimized, I decided to take another stab at it. Now my cold starts are at 2 seconds. Great improvement, but I'm curious what else I might be able to do on the Docker side. Thanks! On Tuesday, May 5, 2020

[google-appengine] Re: Google Cloud Run Container Status

2020-05-05 Thread Jason Collins
I believe you can just delay listening on $PORT until you're ready to receive traffic. On Tuesday, 5 May 2020 05:01:33 UTC-7, Rodrigo Silveira wrote: > > I realize this is not the Cloud Run group, but that's the closest to it. > > I've asked my question on Stackoverflow, but the solution(s)