Dockerless python and libraries

[Jeff Schnitzer]

I'm a little puzzled how this is intended to work. In sandboxed env, I specified 'libraries:' to get PIL. This appears to be ignored in the world of Managed VMs, and the documentation suggests that I update the Dockerfile which is created in my project dir. However, when doing a dockerless deploy (which is AWESOME thank you!) it creates no such file. I can't figure out exactly what I'm supposed to do.

Are libraries a pending feature or am I just missing something obvious?

Thanks,

Jeff

[pdknsk]

However, when doing a dockerless deploy (which is AWESOME thank you!) it creates no such file. I can't figure out exactly what I'm supposed to do.

The file is created when you use -gcloud preview app run- not deploy. The documentation is a bit confusing on this. Alternatively, the default file for each runtime is in google-cloud-sdk/./lib/googlecloudsdk/appengine/dockerfiles/ also.

The libraries concept doesn't apply because the managed VM has full access to the system. If the library is installed, it can be imported.

[pdknsk]

The libraries concept doesn't apply because the managed VM has full access to the system. If the library is installed, it can be imported.

I meant the runtime has full access.

[Jeff Schnitzer]

Ah, thanks! Works great.

If it helps anyone, adding PIL is simply this Dockerfile:

FROM gcr.io/google_appengine/python-compat

RUN apt-get update && apt-get install -y python-imaging

ADD . /app