After installation starting the app hangs on

[homofortis]

Expected behavior

Actual behavior

Information

Diagnostic ID: DCE04336-8053-4026-87FD-CBFB6D23258E
Docker for Mac: 1.12.0-a (Build 11213)
macOS: Version 10.11.6 (Build 15G1004)
[ERROR] docker-cli
docker ps failed
[OK] app
[OK] moby-syslog
[OK] disk
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[ERROR] moby
/Users/zardoz/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
[ERROR] driver.amd64-linux
Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running

Steps to reproduce

1. ...
2. ...

[mchiang0610]

Merging with #119

[samoht]

Detected symptom of problem 'processor-not-supported' in DCE04336-8053-4026-87FD-CBFB6D23258E/20160909-210541.

Your system do not satisfy the hardware requirements of Docker for Mac. nSee https://docs.docker.com/docker-for-mac/#/what-to-know-before-you-install for more information.

The following log matches:

Sep  9 19:35:53 hackBookPro Docker[com.docker.driver.amd64-linux][10044] <Notice>: Launched[10047]: /Applications/Docker.app/Contents/MacOS/com.docker.hyperkit -A -m 2G -c 2 -u -s 0:0,hostbridge -s 31,lpc -s 2:0,virtio-vpnkit,uuid=78cbf5b6-1292-4cb5-b933-4dbbe5f1b5a7,path=/Users/zardoz/Library/Containers/com.docker.docker/Data/s50,macfile=/Users/zardoz/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/mac.0 -s 3,virtio-blk,file:///Users/zardoz/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2,format=qcow -s 4,virtio-9p,path=/Users/zardoz/Library/Containers/com.docker.docker/Data/s40,tag=db -s 5,virtio-rnd -s 6,virtio-9p,path=/Users/zardoz/Library/Containers/com.docker.docker/Data/s51,tag=port -s 7,virtio-sock,guest_cid=3,path=/Users/zardoz/Library/Containers/com.docker.docker/Data,guest_forwards=2376;1525 -l com1,autopty=/Users/zardoz/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty,log=/Users/zardoz/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring -f kexec,/Applications/Docker.app/Contents/Resources/moby/vmlinuz64,/Applications/Docker.app/Contents/Resources/moby/initrd.img,earlyprintk=serial console=ttyS0 com.docker.driver="com.docker.driver.amd64-linux", com.docker.database="com.docker.driver.amd64-linux" ntp=gateway mobyplatform=mac -F /Users/zardoz/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/hypervisor.pid
Sep  9 19:35:53 hackBookPro Docker[com.docker.driver.amd64-linux][10044] <Notice>: Unable to create VM (-85377018)
Sep  9 19:35:53 hackBookPro Docker[com.docker.driver.amd64-linux][10044] <Notice>: vmx_init: processor not supported by Hypervisor.framework
Sep  9 19:35:53 hackBookPro Docker[com.docker.osx.hyperkit.linux][10036] <Notice>: Reap com.docker.driver.amd64-linux (pid 10044): exit status 0
Sep  9 19:35:53 hackBookPro Docker[com.docker.helper][10035] <Notice>: launching...
Sep  9 19:35:53 hackBookPro Docker[com.docker.helper][10035] <Notice>: accessing preferences...
Sep  9 19:35:53 hackBookPro Docker[com.docker.helper][10035] <Notice>: bundle path: /Applications/Docker.app/Contents/Library/LoginItems/DockerHelper.app
Sep  9 19:35:53 hackBookPro Docker[com.docker.helper][10035] <Notice>: auto start: true

[homofortis]

@samoht thank you for your reply. I solved it by enabling Intel virtualization at bios.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked