As I understand it, the python runtime in the flexible environment is essentially using the gcr.io/google-appengine/python docker image referred to in the custom runtime documentation <https://cloud.google.com/appengine/docs/flexible/custom-runtimes/build#configuring_the_dockerfile> except with an ENTRYPOINT <https://docs.docker.com/engine/reference/builder/#entrypoint> specified in the app.yaml. We can see in the linked Dockerfile repository that 'pip install -r /app/requirements.txt' is executed with RUN which occurs at build time, thus before the image is run as a container.
If this was otherwise done when instances were created, it would add significant start up time and run the risk of having inconsistent application containers as dependencies fetched at a later time may result in different packages if versions are not explicit. On Thursday, March 2, 2017 at 7:25:09 PM UTC-5, Nickolas Daskalou wrote: > > Hi, > > For Python runtimes on App Engine flex, are the entries in > requirements.txt > <https://cloud.google.com/appengine/docs/flexible/python/runtime> > installed by pip during the deployment process (and then stored in a saved > image, whereby that image is then simply duplicated when needing to scaling > out), or are they installed by pip during a scale out event (i.e. when the > App Engine scheduler decides it needs a new instance of a service)? > > Thanks, > Nick > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/aa398dae-4a4e-4d33-8416-331046158b07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
