{"action":"created","issue":{"url":"https://api.github.com/repos/SeleniumHQ/docker-selenium/issues/74","labels_url":"https://api.github.com/repos/SeleniumHQ/docker-selenium/issues/74/labels{/name}","comments_url":"https://api.github.com/repos/SeleniumHQ/docker-selenium/issues/74/comments","events_url":"https://api.github.com/repos/SeleniumHQ/docker-selenium/issues/74/events","html_url":"https://github.com/SeleniumHQ/docker-selenium/issues/74","id":92128767,"number":74,"title":"How to use this?","user":{"login":"kevinquillen","id":362176,"avatar_url":"https://avatars.githubusercontent.com/u/362176?v=3","gravatar_id":"","url":"https://api.github.com/users/kevinquillen","html_url":"https://github.com/kevinquillen","followers_url":"https://api.github.com/users/kevinquillen/followers","following_url":"https://api.github.com/users/kevinquillen/following{/other_user}","gists_url":"https://api.github.com/users/kevinquillen/gists{/gist_id}","starred_url":"https://api.github.com/users/kevinquillen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kevinquillen/subscriptions","organizations_url":"https://api.github.com/users/kevinquillen/orgs","repos_url":"https://api.github.com/users/kevinquillen/repos","events_url":"https://api.github.com/users/kevinquillen/events{/privacy}","received_events_url":"https://api.github.com/users/kevinquillen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-06-30T15:46:43Z","updated_at":"2015-07-09T21:21:49Z","closed_at":null,"body":"How exactly do I get this running correctly on OSX? I have boot2docker installed and when I run docker pull or docker run, sometimes it starts up, sometimes I get a certificate error (which I have to wipe all and restart docker).\r\n\r\nI also get this error sometimes:\r\n\r\n```\r\nAn error occurred trying to connect: Post https://192.168.59.103:2376/v1.19/containers/create: dial tcp 192.168.59.103:2376: i/o timeout\r\n```\r\n\r\nSo when I do get the docker image running, attempts to connect to it over VNC fail."},"comment":{"url":"https://api.github.com/repos/SeleniumHQ/docker-selenium/issues/comments/120147651","html_url":"https://github.com/SeleniumHQ/docker-selenium/issues/74#issuecomment-120147651","issue_url":"https://api.github.com/repos/SeleniumHQ/docker-selenium/issues/74","id":120147651,"user":{"login":"rubytester","id":569544,"avatar_url":"https://avatars.githubusercontent.com/u/569544?v=3","gravatar_id":"","url":"https://api.github.com/users/rubytester","html_url":"https://github.com/rubytester","followers_url":"https://api.github.com/users/rubytester/followers","following_url":"https://api.github.com/users/rubytester/following{/other_user}","gists_url":"https://api.github.com/users/rubytester/gists{/gist_id}","starred_url":"https://api.github.com/users/rubytester/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rubytester/subscriptions","organizations_url":"https://api.github.com/users/rubytester/orgs","repos_url":"https://api.github.com/users/rubytester/repos","events_url":"https://api.github.com/users/rubytester/events{/privacy}","received_events_url":"https://api.github.com/users/rubytester/received_events","type":"User","site_admin":false},"created_at":"2015-07-09T21:21:49Z","updated_at":"2015-07-09T21:21:49Z","body":"I lied. I used boot2docker 1.6.2 but when I upgraded to 1.7.0 all fell apart due to this issue: https://github.com/boot2docker/boot2docker/issues/824 (lots of comments as of last 2 weeks)\r\n\r\nI have switched to `docker-machine` (5 days ago) which uses boot2docker parts behind the scene. no issues yet. Mabye becase I created a new vm.\r\n\r\nAnyway: Give docker-machine a try. \r\n\r\nwith brew: \r\n\r\n```\r\nbrew cask install virtualbox\r\nbrew install docker\r\nbrew install docker-machine\r\n```\r\n\r\nFollowed by setup\r\n\r\n```\r\ndocker-machine create --driver virtualbox dev\r\ndocker-machine start\r\neval \"$(docker-machine env dev)\"\r\n```\r\n\r\nAnd now your ip is `docker-machine ip dev`.\r\n\r\nStick the `eval \"$(docker-machine env dev)\"` in ~/.bash_profile or equivalent.\r\n\r\nI also made me a quick shortcut helper file `~/bin/docker-helper.sh`\r\n\r\n\r\n```shell\r\n# source this in your ~/.bash_profile\r\n# for mac os x\r\n\r\nalias d=docker\r\nalias dm=docker-machine\r\n\r\n###############  DOCKER MACHINE vm and it's env\r\n\r\nexport DOCKER_MACHINE_NAME=dev\r\n\r\n# create vm and set up shell env\r\nfunction d-machine-create(){\r\n  docker-machine create --driver virtualbox $DOCKER_MACHINE_NAME\r\n  d-env\r\n}\r\n\r\n# shell env for machine\r\nfunction d-env(){\r\n  echo \"DOCKER_MACHINE_NAME=$DOCKER_MACHINE_NAME\"\r\n  eval \"$(docker-machine env $DOCKER_MACHINE_NAME)\"\r\n  docker info\r\n  echo \"*** ALL LATEST CONTAINERS\"\r\n  docker ps -l -s\r\n}\r\n\r\n# up machine\r\nfunction d-up(){\r\n  docker-machine start $DOCKER_MACHINE_NAME\r\n  d-sh\r\n}\r\n\r\n# down machine\r\nfunction d-down(){\r\n  docker-machine stop $DOCKER_MACHINE_NAME\r\n}\r\n\r\nfunction d-ssh(){\r\n  docker-machine ssh $DOCKER_MACHINE_NAME\r\n}\r\n\r\n############### CONTAINERS AND IMAGES\r\n\r\n# remove stopped container and untagged images\r\nfunction d-clean(){\r\n  docker ps -qa --filter status=exited | xargs -L1 docker rm\r\n  docker images --filter dangling=true -q | xargs -L1 docker rmi\r\n}\r\n\r\n# stop all running containers\r\nfunction d-stop(){\r\n  docker ps -q | xargs -L1 docker stop\r\n}\r\n\r\n# remove all images\r\nfunction d-nuke(){\r\n  docker images -aq | xargs -L1 docker rmi -f\r\n}\r\n```\r\n\r\n\r\nhope this helps you get started.\r\n"}}