{"action":"created","issue":{"url":"https://api.github.com/repos/docker/for-mac/issues/2885","repository_url":"https://api.github.com/repos/docker/for-mac","labels_url":"https://api.github.com/repos/docker/for-mac/issues/2885/labels{/name}","comments_url":"https://api.github.com/repos/docker/for-mac/issues/2885/comments","events_url":"https://api.github.com/repos/docker/for-mac/issues/2885/events","html_url":"https://github.com/docker/for-mac/issues/2885","id":320965712,"number":2885,"title":"Docker not running on Mac after install","user":{"login":"mateuslongo","id":22989787,"avatar_url":"https://avatars0.githubusercontent.com/u/22989787?v=4","gravatar_id":"","url":"https://api.github.com/users/mateuslongo","html_url":"https://github.com/mateuslongo","followers_url":"https://api.github.com/users/mateuslongo/followers","following_url":"https://api.github.com/users/mateuslongo/following{/other_user}","gists_url":"https://api.github.com/users/mateuslongo/gists{/gist_id}","starred_url":"https://api.github.com/users/mateuslongo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mateuslongo/subscriptions","organizations_url":"https://api.github.com/users/mateuslongo/orgs","repos_url":"https://api.github.com/users/mateuslongo/repos","events_url":"https://api.github.com/users/mateuslongo/events{/privacy}","received_events_url":"https://api.github.com/users/mateuslongo/received_events","type":"User","site_admin":false},"labels":[{"id":920265885,"url":"https://api.github.com/repos/docker/for-mac/labels/version/18.03.1-ce-mac65","name":"version/18.03.1-ce-mac65","color":"ededed","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-07T21:33:11Z","updated_at":"2018-05-08T02:32:30Z","closed_at":"2018-05-07T22:46:04Z","author_association":"NONE","body":"<!--\r\nPlease, check https://docs.docker.com/docker-for-mac/troubleshoot/.\r\nIssues without logs and details cannot be debugged, and will be closed.\r\n\r\nReplace `- [ ]` with `- [x]`, or click after having submitted the issue.\r\n-->\r\n\r\n  - [X ] I have tried with the latest version of my channel (Stable or Edge)\r\n  - [X ] I have submitted Diagnostics\r\n  - [X ] I have included the Diagnostics ID in this Issue\r\n  - macOS Version: High Sierra 10.13.4\r\n\r\n### Expected behavior\r\nInstallation completed\r\n### Actual behavior\r\nThis error appeared: Failed to install symlinks in /usr/local/bin (stage 5)\r\n### Information\r\n\r\n<!--  - Full output of the diagnostics from \"Diagnose & Feedback\" in the menu ... -->\r\n```\r\nDiagnostic ID: 7746F600-5EC9-440E-A14C-F717B338BB6D\r\n\r\n\r\nDocker for Mac: version: 18.03.1-ce-mac65 (dd2831d4b7421cf559a0881cc7a5fdebeb8c2b98)\r\nmacOS: version 10.13.4 (build: 17E202)\r\nlogs: /tmp/7746F600-5EC9-440E-A14C-F717B338BB6D/20180507-152943.tar.gz\r\nfailure: No Docker.qcow2 or Docker.raw found: the VM has never been started\r\n[ERROR]  vpnkit\r\n         Unexpected error ((Failure\r\n  \"Error connecting socket to 9p endpoint unix:/Users/mateus/Library/Containers/com.docker.docker/Data/s51: Unix.Unix_error(Unix.ENOENT, \\\"connect\\\", \\\"\\\")\")) connecting to /Users/mateus/Library/Containers/com.docker.docker/Data/s51\r\n         com.docker.vpnkit is not running\r\n         vpnkit check failed with: Unix.Unix_error(Unix.ENOENT, \"connect\", \"\")\r\n[OK]     vmnetd\r\n[OK]     dns\r\n[ERROR]  driver.amd64-linux\r\n         com.docker.driver.amd64-linux is not running\r\n[OK]     virtualization VT-X\r\n[OK]     app\r\n[ERROR]  moby\r\n         /Users/mateus/Library/Containers/com.docker.docker/Data/vms/0/console-ring does not exist\r\n[OK]     system\r\n[OK]     moby-syslog\r\n[OK]     kubernetes\r\n[OK]     files\r\n[OK]     env\r\n[OK]     virtualization kern.hv_support\r\n[ERROR]  osxfs\r\n         com.docker.osxfs is not running\r\n[OK]     moby-console\r\n[OK]     logs\r\n[ERROR]  docker-cli\r\n         cannot find docker\r\n         /var/run/docker.sock does not exist\r\n         Unexpected error (No such file or directory) connecting to /var/run/docker.sock\r\n         /Users/mateus/Library/Containers/com.docker.docker/Data/s60 does not exist\r\n         Unexpected error (No such file or directory) connecting to /Users/mateus/Library/Containers/com.docker.docker/Data/s60\r\n         docker ps failed\r\n[ERROR]  disk\r\n         No Docker.qcow2 or Docker.raw found: the VM has never been started\r\n\r\n\r\n```\r\n<!--\r\n  - A reproducible case if this is a bug, Dockerfiles FTW\r\n  - Page URL if this is a docs issue or the name of a man page\r\n  -->\r\n\r\n### Steps to reproduce the behavior\r\n\r\n  1. Install Docker for mac\r\n  2. Run Docker\r\n  3. Run again and start diagnostics tool.\r\n  \r\n"},"comment":{"url":"https://api.github.com/repos/docker/for-mac/issues/comments/387265508","html_url":"https://github.com/docker/for-mac/issues/2885#issuecomment-387265508","issue_url":"https://api.github.com/repos/docker/for-mac/issues/2885","id":387265508,"user":{"login":"YRM64","id":32690260,"avatar_url":"https://avatars1.githubusercontent.com/u/32690260?v=4","gravatar_id":"","url":"https://api.github.com/users/YRM64","html_url":"https://github.com/YRM64","followers_url":"https://api.github.com/users/YRM64/followers","following_url":"https://api.github.com/users/YRM64/following{/other_user}","gists_url":"https://api.github.com/users/YRM64/gists{/gist_id}","starred_url":"https://api.github.com/users/YRM64/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/YRM64/subscriptions","organizations_url":"https://api.github.com/users/YRM64/orgs","repos_url":"https://api.github.com/users/YRM64/repos","events_url":"https://api.github.com/users/YRM64/events{/privacy}","received_events_url":"https://api.github.com/users/YRM64/received_events","type":"User","site_admin":false},"created_at":"2018-05-08T02:32:30Z","updated_at":"2018-05-08T02:32:30Z","author_association":"NONE","body":"Mateuslongo,\r\nThere are a ton of reasons why Docker won't start after installation.  And, sometimes the reason is something puzzling such as Docker won't finish starting.  I, myself waited hours for Docker to finish starting one day, and I said to myself \"we seriously need something new for Mac users.\" I reinstalled Docker three times, and each time Docker wouldn't finish starting.  But to get to the root of it all, the logs pretty much help identify specific problems.  \r\n\r\nWhat we can do:\r\n1 ) Use our Macs console for log queries 2) Make sure our certificates are set up correctly\r\n3) Docker for Mac won't start up if the Mac user account and the home folder are renamed after we install our application 4) Project directories outside /Users - affects file sharing and volume mounting \r\n5) incompatible CPUs can be problematic\r\n\r\nI used my own situation as an example above, and yet the tutorials indicated that if Docker still fails to start:  make sure to quit Docker before installing a new version.  I not only quit Docker but I dragged it to the trash bin because I didn't have access to the menu.  I never had the Docker daemon running so that wasn't an issue, and couldn't run the uninstall commands from the menu because I had no menu.  I didn't have access to Docker environment variables.  NPM would inconsistently report that I had Docker one day, and the next day I had no Docker.  For the days it reported I had Docker, I never had access to the Docker menu/dialogue access box to orchestrate my configurations.  And, one of the troubleshooting tips I didn't have the opportunity to try before my laptop went on the blink was the ability to run ls of -i tcp:8080.  As I read the blogs and visit Github, some of the same troubleshooting tips that worked for some, didn't work for others.  Sometimes, it appeared to be consistency in terms of what worked, and what didn't work.  But what I came to realize is that we all have a tendency to interpret, manifest, and describe events a little bit differently than one another and often times that's what makes the difference in something working on my Mac vs. something working on yours.  As a consequence, I pay close attention to how folks express their experiences with Docker, and often times find myself sharing in their experiences.  Pleased to know you were able to find resolution."}}
{"actor":{"display_login":"YRM64"}}