{"action":"opened","issue":{"url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/253","labels_url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/253/labels{/name}","comments_url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/253/comments","events_url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/253/events","html_url":"https://github.com/eris-ltd/eris-cli/issues/253","id":107119410,"number":253,"title":"`eris init` bugs (not seeing stopped VM + quitting immediately)","user":{"login":"taoeffect","id":138706,"avatar_url":"https://avatars.githubusercontent.com/u/138706?v=3","gravatar_id":"","url":"https://api.github.com/users/taoeffect","html_url":"https://github.com/taoeffect","followers_url":"https://api.github.com/users/taoeffect/followers","following_url":"https://api.github.com/users/taoeffect/following{/other_user}","gists_url":"https://api.github.com/users/taoeffect/gists{/gist_id}","starred_url":"https://api.github.com/users/taoeffect/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/taoeffect/subscriptions","organizations_url":"https://api.github.com/users/taoeffect/orgs","repos_url":"https://api.github.com/users/taoeffect/repos","events_url":"https://api.github.com/users/taoeffect/events{/privacy}","received_events_url":"https://api.github.com/users/taoeffect/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-18T02:35:22Z","updated_at":"2015-09-18T02:35:22Z","closed_at":null,"body":"On latest `develop` c8624a0, I've got this `eris` VM that's stopped, so I type `eris init. It thinks there is no VM and asks to create it. I tell it go ahead, and it does something very confusing:\r\n\r\n- It says \"This will take some time, please feel free to go feed your marmot.\"\r\n- It then immediately quits.\r\n\r\nSo this seems like two bugs:\r\n\r\n1. It should have spotted the stopped VM and tried to start it.\r\n2. For whatever reason, after I told it it could create a VM, it quit immediately with a very specific message that gave me the user (me) the impression that it spawned a background process that would handle things, but it didn't, it just quit.\r\n\r\nThis indicates something important: long-running commands should never have a case where they say \"this will take some time, go feed your marmot\", and then immediately quit, because most users will think that that is expected behavior and that everything is fine, when in fact a failure occurred.\r\n\r\n```\r\n-> % docker-machine ls\r\nNAME   ACTIVE   DRIVER       STATE     URL   SWARM\r\neris            virtualbox   Stopped\r\n-> % eris init\r\nThe marmots could not find a docker-machine virtual machine they could connect to.\r\nOur marmots recommend that you have a vm dedicated to eris dev-ing.\r\nWould you like the marmots to create a machine for you? (y/n): y\r\nThe marmots will create an eris machine.\r\nCreating the eris docker-machine.\r\nThis will take some time, please feel free to go feed your marmot.\r\n-> % findit eris\r\n-> % findit docker\r\n-> % docker-machine ls\r\nNAME   ACTIVE   DRIVER       STATE     URL   SWARM\r\neris            virtualbox   Stopped\r\n```"}}