Grafana setup stalling out of the box

[ches]

Hey there,

Neat idea here, but unfortunately I haven't been able to get very far: I've run Vessel, used your tested awvessel/manifest and tried to set up an environment for Grafana. Twice now, it seemingly stalls around the end of the CoreOS VM provisioning—the end of the log is showing:

Running provisioner: file...
Running provisioner: shell...
Running: inline script

Vessel is not completely unresponsive (I can open another Environment window), but the "Starting Virtual Machine" dialog is just spinning indefinitely with no means of bailing out. There are two Atom Helper processes running and chewing up a bit of CPU. vagrant global-status (or Virtualbox GUI) confirms the CoreOS VM is running.

I'll try to debug further if you can give me a little guidance. I'm not acquainted with Atom Shell so at the moment I don't have the free cycles to jump in blindly and try to figure out where relevant code lives without some direction.

On another note, it'd be great if you could write a bit more detail than the FAQ about how you're using Consul in the images in the awvessel/manifest. Gaining some insight on how to utilize CoreOS effectively, potentially for production use too, is one of the most interesting things to me about your Vessel manifest, but as it stands currently it looks like I'll have to wade into finding your Dockerfiles, inspecting Vessel code to grok what exactly "etcd is used to coordinate consul bootstrapping across nodes" means, etc. If I have to dig, that's fine, but since it seems like something that's pretty opinionated in your own manifest, it'd be helpful and educational if you explained it further. Actually I see that the Getting Started doc mentions a Development Environment doc that sounds like what I'm seeking, but perhaps this isn't written yet.

Thanks! 🤘