Ok, based on this thread (
https://code.google.com/p/google-cloud-sdk/issues/detail?id=163) it seems 
that gcloud defaults to "docker-less" local development. Unfortunately, 
when this is the case I can't seem to get application logs to appear in the 
console (or anywhere else for that matter).  I see that it falls back on 
using devappserver2.py / jetty, but I'm not sure where stdout is getting 
redirected.  I do see general request handling logging in the main console 
window, but no application logging gets out.  This is not the case if I use 
mvn gcloud:run which logs just fine (to docker).


Again, if I use mvn gcloud:run, it defaults to using docker, and I am able 
to find my logs by ssh-ing into the running container (in 
/var/logs/appengine).  But when running via 'gcloud preview app run' I get 
no app logs.


So, two questions: 

First, where are the logs when running (dockerless) 'gcloud preview app 
run'?  I have everything set up correctly (and can confirm that app log 
messages are redirected from stdout to file when running within docker 
container via mvn gcloud:run).


Second, is it possible to use the 'gcloud preview app run' with a flag to 
indicate that it should run in docker "mode"?  A flag could be a work 
around for me and would be handy in any case (as I typically launch from 
the gcloud toolset so i can use a dispatcher.yaml and other app.yaml 
modules).


Any insight into this is appreciated. Thanks for the help.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3aac9123-4752-44b7-ae6e-1a681a754ea1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to