Grafana install on Docker in Google Cloud

Grafana installation on Docker in Google cloud freezes after the following messages:

t=2017-05-03T21:20:32+0000 lvl=info msg=“Executing migration” logger=migrator id="add index annotation 1 v3"
t=2017-05-03T21:20:32+0000 lvl=info msg=“Executing migration” logger=migrator id="add index annotation 2 v3"
t=2017-05-03T21:20:33+0000 lvl=info msg=“Executing migration” logger=migrator id="add index annotation 3 v3"
t=2017-05-03T21:20:33+0000 lvl=info msg=“Executing migration” logger=migrator id="add index annotation 4 v3"
t=2017-05-03T21:20:33+0000 lvl=info msg="Created default admin user: [admin]"
t=2017-05-03T21:20:33+0000 lvl=info msg=“Starting plugin search” logger=plugins
t=2017-05-03T21:20:33+0000 lvl=warn msg=“Plugin dir does not exist” logger=plugins dir=/var/lib/grafana/plugins
t=2017-05-03T21:20:33+0000 lvl=info msg=“Plugin dir created” logger=plugins dir=/var/lib/grafana/plugins
t=2017-05-03T21:20:33+0000 lvl=info msg=“Initializing Alerting” logger=alerting.engine
t=2017-05-03T21:20:33+0000 lvl=info msg=“Initializing CleanUpService” logger=cleanup
t=2017-05-03T21:20:33+0000 lvl=info msg="Initializing Stream Manager"
t=2017-05-03T21:20:33+0000 lvl=info msg=“Initializing HTTP Server” logger=http.server address=0.0.0.0:3000 protocol=http subUrl=

Had anybody experience similar behavior?

What do you mean by freezes? In the browser? When using curl? Does the api work: http://localhost:3000/api/search

There are no errors in the log there and after the Initializing HTTP Server message Grafana is usually ready to receive requests.

I am using Google cloud shell for grafana installation and by freezing meant that it was not clear that installation succeeded from the above messages on console. I was expecting something more common like this “…Grafana HTTP server started and listening on port 3000”.

Would you have any recommendation on accessing Grafana from the browser after it started on port 3000. Asking this question since it looks web preview on Google cloud shell is available for only ports 8080-8084

Is it Google Compute Engine (GCE) that you are using?

Maybe this will help:

http://stackoverflow.com/questions/21065922/how-to-open-a-specific-port-such-as-9090-in-google-compute-engine