{"action":"created","issue":{"url":"https://api.github.com/repos/docker/machine/issues/1805","labels_url":"https://api.github.com/repos/docker/machine/issues/1805/labels{/name}","comments_url":"https://api.github.com/repos/docker/machine/issues/1805/comments","events_url":"https://api.github.com/repos/docker/machine/issues/1805/events","html_url":"https://github.com/docker/machine/issues/1805","id":104867141,"number":1805,"title":"No certificate / key created when creating a new docker machine using the aws driver","user":{"login":"bahaaldine","id":820299,"avatar_url":"https://avatars.githubusercontent.com/u/820299?v=3","gravatar_id":"","url":"https://api.github.com/users/bahaaldine","html_url":"https://github.com/bahaaldine","followers_url":"https://api.github.com/users/bahaaldine/followers","following_url":"https://api.github.com/users/bahaaldine/following{/other_user}","gists_url":"https://api.github.com/users/bahaaldine/gists{/gist_id}","starred_url":"https://api.github.com/users/bahaaldine/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bahaaldine/subscriptions","organizations_url":"https://api.github.com/users/bahaaldine/orgs","repos_url":"https://api.github.com/users/bahaaldine/repos","events_url":"https://api.github.com/users/bahaaldine/events{/privacy}","received_events_url":"https://api.github.com/users/bahaaldine/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-09-04T10:39:30Z","updated_at":"2015-09-28T22:17:06Z","closed_at":"2015-09-09T17:25:32Z","body":"Hi,\r\n\r\nSo I'm running docker-machine 0.4.1 and I'm basically trying to create a docker-machine on AWS.\r\nThe creation works, I can see my VM spinning up on AWS, but I can't switch my default machine on it, meaning the following command:\r\n\r\n```bash\r\ndocker-machine env docker-machine-i1\r\n```\r\nreturns:\r\n\r\n```bash\r\nopen /Users/bahaaldine/.docker/machine/machines/docker-machine-i1/ca.pem: no such file or directory\r\n```\r\n\r\nA docker-machine ls gives:\r\n```bash\r\nNAME                ACTIVE   DRIVER       STATE     URL                         SWARM\r\ndefault                      *        virtualbox   Running   tcp://192.168.99.100:2376   \r\ndocker-machine-i1            amazonec2    Running   tcp://XXX.XXX.XXX.XXX:2376 \r\n```\r\n\r\nThis is how I've created the AWS machine:\r\n```bash\r\ndocker-machine -D create \\\r\n    --driver amazonec2 \\\r\n    --amazonec2-access-key $AWS_ACCESS_KEY \\\r\n    --amazonec2-secret-key $AWS_SECRET_KEY \\\r\n    --amazonec2-vpc-id $AWS_VPC_ID \\\r\n    --amazonec2-zone b \\\r\n    docker-machine-i1\r\n```\r\n\r\nWhen I compare the content of \r\n```bash\r\n/Users/bahaaldine/.docker/machine/machines/default\r\n```\r\nto \r\n```bash\r\n/Users/bahaaldine/.docker/machine/machines/docker-machine-i1\r\n```\r\nFollowing files are missing:\r\n\r\n```bash\r\nca.pem\r\ncert.pem\r\nserver.pem\r\nserver-key.pem\r\n```\r\nMy default environment variable are configured like following:\r\n```bash\r\nexport DOCKER_HOST=tcp://192.168.99.100:2376\r\nexport DOCKER_CERT_PATH=/Users/bahaaldine/.docker/machine/machines/default\r\nexport DOCKER_MACHINE_NAME=default\r\nexport DOCKER_TLS_VERIFY=1\r\n```\r\n\r\nStill an :\r\n```bash\r\neval \"$(docker-machine env docker-machine-i1)\"\r\n```\r\ngives:\r\n```\r\nopen /Users/bahaaldine/.docker/machine/machines/docker-machine-i1/ca.pem: no such file or directory\r\n```\r\n\r\nAny thoughts?\r\n\r\nThanks,\r\nBaha"},"comment":{"url":"https://api.github.com/repos/docker/machine/issues/comments/143889280","html_url":"https://github.com/docker/machine/issues/1805#issuecomment-143889280","issue_url":"https://api.github.com/repos/docker/machine/issues/1805","id":143889280,"user":{"login":"fourty7","id":6901944,"avatar_url":"https://avatars.githubusercontent.com/u/6901944?v=3","gravatar_id":"","url":"https://api.github.com/users/fourty7","html_url":"https://github.com/fourty7","followers_url":"https://api.github.com/users/fourty7/followers","following_url":"https://api.github.com/users/fourty7/following{/other_user}","gists_url":"https://api.github.com/users/fourty7/gists{/gist_id}","starred_url":"https://api.github.com/users/fourty7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fourty7/subscriptions","organizations_url":"https://api.github.com/users/fourty7/orgs","repos_url":"https://api.github.com/users/fourty7/repos","events_url":"https://api.github.com/users/fourty7/events{/privacy}","received_events_url":"https://api.github.com/users/fourty7/received_events","type":"User","site_admin":false},"created_at":"2015-09-28T22:17:05Z","updated_at":"2015-09-28T22:17:05Z","body":"I'm unsure how running `eval \"$(docker-machine env default --shell  bash)\"` is a resolution to this issue. I'm having this same issue where it's not able to generate the certificates and the way that I go about figuring out that the certs haven't been generated is by running the above command:\r\n\r\n`eval \"$(docker-machine env default --shell bash)\"\r\nopen C:\\Users\\{user}\\.docker\\machine\\machines\\default\\ca.pem: The system cannot find the file specified.`\r\n\r\nSo far I have done pretty much everything I can think of to try to generate the certs and everything so far has failed. I've tried `regenerate-certs`, which results in the system just hanging and then doing nothing. I've tried fixing my proxy settings and restarting. I've tried recreating the vm several times.\r\n\r\nI'm genuinely unsure as to what to do next in order to get this to work. As of right now my boot2docker VM can't access the outside world which makes it rather hard to do much of anything with it. The strange part is that I can `docker-machine ssh` into my vm."}}