Expected behavior

I thought this was fixed. Haven't seen it in a bit, but it's back in force!

Actual behavior

400% CPU consumption, not the normal 200-300% I've seen before.

Information

See attached images

Diagnostic ID: 551E9E16-E61E-454A-AE28-EC96A1C7537F
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.10.5 (Build 14F1808)
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

Creating a docker image via docker-compose up

Actual behavior

Step 9 : ADD Gemfile /myapp/Gemfile
---> 09a5fd9d54e8
ERROR: Service 'kcs' failed to build: {u'stream': u' ---> 09a5fd9d54e8\n'}
docker-compose up
ERROR: Bad response from Docker engine

Information

The docker deamon doesnt strart
Diagnostic ID: 285B74E3-14F5-4AED-83A9-263F76942063
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

Service information pretty-printed to console

Actual behavior

Runtime error

➜  docker service inspect --pretty swarmbundle_web
ID:     de179gar9d0o7ltdybungplod
Name:       swarmbundle_web
Labels:
 - com.docker.stack.namespace=swarmbundle
Mode:       Replicated
 Replicas:  2
Placement:
UpdateConfig:
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0 pc=0x4333ccb]

goroutine 1 [running]:
panic(0x47ee2a0, 0xc8200100e0)
    /usr/local/go/src/runtime/panic.go:481 +0x3e6
github.com/docker/docker/api/client/service.printService(0x5a44198, 0xc82007e008, 0xc8200122e0, 0x19, 0x13b, 0xecf2e2b14, 0x3104b62f, 0x4d29780, 0xecf2f27d5, 0x34878f30, ...)
    /go/src/github.com/docker/docker/api/client/service/inspect.go:121 +0x1d8b
github.com/docker/docker/api/client/service.printHumanFriendly(0x5a44198, 0xc82007e008, 0xc820333d00, 0x1, 0x2, 0xc82034acf0, 0x0, 0x0)
    /go/src/github.com/docker/docker/api/client/service/inspect.go:75 +0x19d
github.com/docker/docker/api/client/service.runInspect(0xc82009e510, 0xc820333d00, 0x1, 0x2, 0x0, 0x0, 0x1, 0x0, 0x0)
    /go/src/github.com/docker/docker/api/client/service/inspect.go:66 +0x239
github.com/docker/docker/api/client/service.newInspectCommand.func1(0xc820329440, 0xc820333d00, 0x1, 0x2, 0x0, 0x0)
    /go/src/github.com/docker/docker/api/client/service/inspect.go:40 +0xd9
github.com/spf13/cobra.(*Command).execute(0xc820329440, 0xc820333bc0, 0x2, 0x2, 0x0, 0x0)
    /go/src/github.com/docker/docker/vendor/src/github.com/spf13/cobra/command.go:593 +0x6fe
github.com/spf13/cobra.(*Command).ExecuteC(0xc820071b00, 0xc820329440, 0x0, 0x0)
    /go/src/github.com/docker/docker/vendor/src/github.com/spf13/cobra/command.go:683 +0x55c
github.com/spf13/cobra.(*Command).Execute(0xc820071b00, 0x0, 0x0)
    /go/src/github.com/docker/docker/vendor/src/github.com/spf13/cobra/command.go:642 +0x2d
github.com/docker/docker/cli/cobraadaptor.CobraAdaptor.run(0xc820071b00, 0xc82009e510, 0x7fff5fbffaf7, 0x7, 0xc820082020, 0x3, 0x3, 0x0, 0x0)
    /go/src/github.com/docker/docker/cli/cobraadaptor/adaptor.go:118 +0x25f
github.com/docker/docker/cli/cobraadaptor.CobraAdaptor.Command.func1(0xc820082020, 0x3, 0x3, 0x0, 0x0)
    /go/src/github.com/docker/docker/cli/cobraadaptor/adaptor.go:126 +0x8c
github.com/docker/docker/cli.(*Cli).Run(0xc82034a660, 0xc820082010, 0x4, 0x4, 0x0, 0x0)
    /go/src/github.com/docker/docker/cli/cli.go:81 +0x34b
main.main()
    /go/src/github.com/docker/docker/cmd/docker/docker.go:72 +0x599

➜  docker service ls
ID            NAME               REPLICAS  IMAGE                                                                                         COMMAND
42wc6rtrcxay  swarmbundle_redis  2/2       redis@sha256:b50f15d427aea5b579f9bf972ab82ff8c1c47bffc0481b225c6a714095a9ec34
de179gar9d0o  swarmbundle_web    2/2       neofreko/flask-hello@sha256:817175eb246636d202ce2f85ae98ea1592cc22450abe5ff695dfb0762394d5af

➜  docker service inspect swarmbundle_web
[
    {
        "ID": "de179gar9d0o7ltdybungplod",
        "Version": {
            "Index": 315
        },
        "CreatedAt": "2016-07-30T04:59:00.822392367Z",
        "UpdatedAt": "2016-07-30T22:57:25.881299248Z",
        "Spec": {
            "Name": "swarmbundle_web",
            "Labels": {
                "com.docker.stack.namespace": "swarmbundle"
            },
            "TaskTemplate": {
                "ContainerSpec": {
                    "Image": "neofreko/flask-hello@sha256:817175eb246636d202ce2f85ae98ea1592cc22450abe5ff695dfb0762394d5af"
                }
            },
            "Mode": {
                "Replicated": {
                    "Replicas": 2
                }
            },
            "Networks": [
                {
                    "Target": "5vpyomhb6ievnk0i0o60gcnei",
                    "Aliases": [
                        "web"
                    ]
                }
            ],
            "EndpointSpec": {
                "Mode": "vip",
                "Ports": [
                    {
                        "Protocol": "tcp",
                        "TargetPort": 5000
                    }
                ]
            }
        },
        "Endpoint": {
            "Spec": {
                "Mode": "vip",
                "Ports": [
                    {
                        "Protocol": "tcp",
                        "TargetPort": 5000
                    }
                ]
            },
            "Ports": [
                {
                    "Protocol": "tcp",
                    "TargetPort": 5000,
                    "PublishedPort": 30000
                }
            ],
            "VirtualIPs": [
                {
                    "NetworkID": "6o4107cj2jx9tihgb0jyts6pj",
                    "Addr": "10.255.0.4/16"
                },
                {
                    "NetworkID": "5vpyomhb6ievnk0i0o60gcnei",
                    "Addr": "10.0.1.2/24"
                }
            ]
        },
        "UpdateStatus": {
            "StartedAt": "0001-01-01T00:00:00Z",
            "CompletedAt": "0001-01-01T00:00:00Z"
        }
    }
]

Information

Diagnostic ID: B89DA7DC-71FF-437E-B968-4B16D3AE87B7
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.4 (Build 15E65)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. deploy service using bundle. Made from this compose file:

   version: '2'
   services:
   web:
       image: neofreko/flask-hello
       ports:
       - "5000"
       depends_on:
       - redis
   redis:
       image: redis
   

2. inspect deployed service

Expected behavior

Actual behavior

Information

Diagnostic ID: 06B5623F-C787-4790-A610-2C1DD056E058
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.6 (Build 15G31)
[ERROR] docker-cli
docker ps failed
[OK] app
[OK] moby-syslog
[ERROR] disk
disk check failed with: Failure("exec: /Applications/Docker.app/Contents/Resources/bin/../../../Contents/MacOS/qemu-img check /Volumes/Macintosh HD/Users/BHendriksen/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 > /tmp/06B5623F-C787-4790-A610-2C1DD056E058/20160730-005353/qemu-img-check.stdout 2> /tmp/06B5623F-C787-4790-A610-2C1DD056E058/20160730-005353/qemu-img-check.stderr: exit 1")
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

Running commands without errors

Actual behavior

I'm testing build service inside docker container and sometimes getting messages like:

tail: /home/dev/root-linux/build/build.log: Transport endpoint is not connected
tail: '/home/dev/root-linux/build/build.log' has become inaccessible: Transport endpoint is not connected
dev@8e9f8a301878:~/root-linux$
dev@8e9f8a301878:~/root-linux$ Error response from daemon: dial unix /Users/bzt/Library/Containers/com.docker.docker/Data/*00000003.00000948: connect: connection refused

after which container quits. It happens sporadically, more likely for long running commands.

The /home/dev is a volume mounted from host.

Information

Diagnostic ID: BAB087EC-07AD-4E71-8D1B-2FE0299DB55F
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

Have not found reliable steps to reproduce yet.

Information

When Docker 1.11 was run via docker-machine inside Virtualbox, we had the ability to share the USB port. For Android developers, it was useful for setting up a build server and connecting Android devices to it so that you could run unit tests on the connected devices.

Now, it no longer appears to be possible w/ Docker 1.12. I had to dig a lot before I could find out that this doesn't work at all w/ Docker 1.12 :(
https://forums.docker.com/t/usb-devices-with-private-beta-on-os-x/9951/4

Also, the Android emulators have compatibility issues when Docker 1.12 is running.
Genymotion doesn't work because Virtualbox can't run at the same time as OSX's Hypervisor.
The official Android emulators use QEMU which also currently isn't compatible w/ OSX's Hypervisor.

Basically, if you're an Android developer who is trying to run a dev version of the server or run a Jenkins build server on the same machine, it won't work. You're better off running Genymotion emulators and the older Docker 1.11 on Virtualbox if you need to run everything on the same machine.

Expected behavior

Actual behavior

Information

Diagnostic ID: C35AE4C4-DD0E-4544-84E6-7D7E5259D786
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[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/master/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. ...

Expected behavior

Actual behavior

Information

Diagnostic ID: BA5FCDEC-9871-4011-90B0-DEF85F1CA7CA
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[ERROR] docker-cli
/var/run/docker.sock does not exist
Unexpected error (No such file or directory) connecting to /var/run/docker.sock
/Users/ishouvik/Library/Containers/com.docker.docker/Data/s60 does not exist
Unexpected error (No such file or directory) connecting to /Users/ishouvik/Library/Containers/com.docker.docker/Data/s60
docker ps failed
[OK] app
[OK] moby-syslog
[ERROR] disk
disk check failed with: Failure("exec: /Applications/Docker.app/Contents/Resources/bin/../../../Contents/MacOS/qemu-img check /Users/ishouvik/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 > /tmp/BA5FCDEC-9871-4011-90B0-DEF85F1CA7CA/20160730-014902/qemu-img-check.stdout 2> /tmp/BA5FCDEC-9871-4011-90B0-DEF85F1CA7CA/20160730-014902/qemu-img-check.stderr: exit 1")
[OK] virtualization
[OK] system
[OK] menubar
[ERROR] osxfs
com.docker.osxfs is not running
[ERROR] db
/Users/ishouvik/Library/Containers/com.docker.docker/Data/s40 does not exist
Unexpected error (No such file or directory) connecting to /Users/ishouvik/Library/Containers/com.docker.docker/Data/s40
com.docker.db is not running
[ERROR] slirp
/Users/ishouvik/Library/Containers/com.docker.docker/Data/s51 does not exist
Unexpected error (No such file or directory) connecting to /Users/ishouvik/Library/Containers/com.docker.docker/Data/s51
com.docker.slirp is not running
[OK] moby-console
[OK] logs
[ERROR] vmnetd
Connection refused (ECONNREFUSED) connecting to /var/tmp/com.docker.vmnetd.socket: check if service is running
/private/tmp/vmnetd/com.docker.vmnetd is not running
[OK] env
[ERROR] moby
/Users/ishouvik/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. Try and install Docker

Expected behavior

Docker CLI should have loaded.

Actual behavior

docker is not usable from CLI

Information

Diagnostic ID: 9E1DF185-6F1E-43F7-9A96-0935A3795F8B
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.5 (Build 15F34)
[ERROR] docker-cli
cannot find docker
docker-cli check failed with: Failure("docker -v: timeout after 10.00s")
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

Docker.app launches, credentials entered and docker is available.

Actual behavior

Docker.app launched, but various problems occur, see diagnostic below.

Information

Diagnostic ID: AAA8C546-3218-4527-B3B4-0D4D7352E775
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[ERROR] docker-cli
/var/run/docker.sock does not exist
Unexpected error (No such file or directory) connecting to /var/run/docker.sock
/Users/######/Library/Containers/com.docker.docker/Data/s60 does not exist
Unexpected error (No such file or directory) connecting to /Users/######/Library/Containers/com.docker.docker/Data/s60
docker ps failed
[OK] app
[OK] moby-syslog
[ERROR] disk
disk check failed with: Failure("exec: /Applications/Docker.app/Contents/Resources/bin/../../../Contents/MacOS/qemu-img check /Users/######/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 > /tmp/AAA8C546-3218-4527-B3B4-0D4D7352E775/20160729-192853/qemu-img-check.stdout 2> /tmp/AAA8C546-3218-4527-B3B4-0D4D7352E775/20160729-192853/qemu-img-check.stderr: exit 1")
[OK] virtualization
[OK] system
[OK] menubar
[ERROR] osxfs
com.docker.osxfs is not running
[ERROR] db
/Users/######/Library/Containers/com.docker.docker/Data/s40 does not exist
Unexpected error (No such file or directory) connecting to /Users/######/Library/Containers/com.docker.docker/Data/s40
com.docker.db is not running
[ERROR] slirp
/Users/######/Library/Containers/com.docker.docker/Data/s51 does not exist
Unexpected error (No such file or directory) connecting to /Users/######/Library/Containers/com.docker.docker/Data/s51
com.docker.slirp is not running
[OK] moby-console
[OK] logs
[ERROR] vmnetd
Connection refused (ECONNREFUSED) connecting to /var/tmp/com.docker.vmnetd.socket: check if service is running
/private/tmp/vmnetd/com.docker.vmnetd is not running
[OK] env
[ERROR] moby
/Users/######/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. Download Docker.dmg (Docker for Mac 1.12 stable)
2. Copy Docker.app over to /Applications/ folder
3. Launch the app
4. Enter my user credentials when asked
5. Docker symbol on task bar shows "Docker is running" with green button and a "Restart" button
   All other menu points are disabled.

This is repeatable, have tried several times.

What is weird is that the first line in the Diagnostic field says: "Docker for Mac: version: win-beta-v1.12.0-rc5-beta21-73-g9cd1dc2.

I got access to Docker for Mac beta back in May - I think. Haven't used it much.

How can I tell if there are some BETA components which must be uninstalled ?

Expected behavior

Let me choose to update or not docker automatically.

Actual behavior

docker for Mac doesn't let me tick the option / opt in auto update.

Information

Chances are I have some config broken that is not restored by the 'reset' functionality (as I have used it a lot) or it is related with my user not being a sudoer / Admin.

Currently running Version 1.12.0-rc4-beta20 (build: 10404) 32ce3bdb164320603f1c2d1fb2ba32a43477ef3d, but this problem happened with older versions (at least, beta14).

$ uname -a
Darwin henvic.local 15.6.0 Darwin Kernel Version 15.6.0: Thu Jun 23 18:25:34 PDT 2016; root:xnu-3248.60.10~1/RELEASE_X86_64 x86_64

Expected behavior

run docker-compose up

Actual behavior

$ docker-compose up
Traceback (most recent call last):
File "", line 3, in
File "compose/cli/main.py", line 61, in main
File "compose/cli/main.py", line 113, in perform_command
File "contextlib.py", line 35, in exit
File "compose/cli/errors.py", line 56, in handle_connection_errors
TypeError: log_timeout_error() takes exactly 1 argument (0 given)
docker-compose returned -1

Information

The docker deamon doesnt strart
Diagnostic ID: 285B74E3-14F5-4AED-83A9-263F76942063
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce the behavior

1. docker-compose up

Expected behavior

Actual behavior

Information

Diagnostic ID: 9A75CADC-A905-4520-8F64-C0D1256CDC78
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.10.5 (Build 14F27)
[ERROR] docker-cli
wrong Docker version: 1.9.1 (expected 1.12.0)
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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

docker run -p 8080:8080 -p 50000:50000 -v /Users/joe/jenkins_home:/var/jenkins_home jenkins

Actual behavior

docker run -p 8080:8080 -p 50000:50000 -v /Users/joe/jenkins_home:/var/jenkins_home jenkins
Unable to find image 'jenkins:latest' locally
latest: Pulling from library/jenkins
5c90d4a2d1a8: Pulling fs layer
ab30c63719b1: Pulling fs layer
c6072700a242: Pulling fs layer
5f444d070427: Waiting
620b5227cf38: Waiting
3cfd33220efa: Waiting
864a98a84dd2: Waiting
734cc28150de: Waiting
83a54d30c146: Waiting
ed85ef8f0008: Waiting
2a8cac69db6b: Waiting
48492da1052e: Waiting
ef7ab6cf01e2: Waiting
3ca6002e0b34: Waiting
52763f8fd3fb: Waiting
6f3d535bd7f9: Waiting
78ea3baad232: Waiting
4459c86d81aa: Waiting
docker: open /var/lib/docker/tmp/GetImageBlob027034255: structure needs cleaning.

Information

Diagnostic ID: 1E7D444B-1C9A-4650-BE0C-9A866996623E
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.5 (Build 15F34)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. docker run -p 8080:8080 -p 50000:50000 -v /Users/joe/jenkins_home:/var/jenkins_home jenkins

Expected behavior

Actual behavior

Information

Diagnostic ID: 696CD303-4238-4988-BAC7-356E680020D0
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.6 (Build 15G31)
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

Actual behavior

Information

Diagnostic ID: C66DCF4E-ED06-4A88-83D6-0921B7A7582C
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.5 (Build 15F34)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

As far as I know my Macbook supports Hypervisor

Actual behavior

Docker is claiming my Macbook Pro Mid 2009 does not support Hypervisor:

Incompatible CPU detected
Docker requires a processor with virtualization capabilities.

Information

Diagnostic ID: 4C5B55F0-7F06-419C-903C-E7029E9EE155
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[ERROR] docker-cli
cannot find docker
docker-cli check failed with: Failure("docker -v: timeout after 10.00s")
[OK] app
[OK] moby-syslog
[ERROR] disk
disk check failed with: Failure("exec: /Applications/Docker.app/Contents/Resources/bin/../../../Contents/MacOS/qemu-img check /Users/rponte/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 > /tmp/4C5B55F0-7F06-419C-903C-E7029E9EE155/20160729-002736/qemu-img-check.stdout 2> /tmp/4C5B55F0-7F06-419C-903C-E7029E9EE155/20160729-002736/qemu-img-check.stderr: exit 1")
[OK] virtualization
[OK] system
[OK] menubar
[ERROR] osxfs
com.docker.osxfs is not running
[ERROR] db
/Users/rponte/Library/Containers/com.docker.docker/Data/s40 does not exist
Unexpected error (No such file or directory) connecting to /Users/rponte/Library/Containers/com.docker.docker/Data/s40
com.docker.db is not running
[ERROR] slirp
/Users/rponte/Library/Containers/com.docker.docker/Data/s51 does not exist
Unexpected error (No such file or directory) connecting to /Users/rponte/Library/Containers/com.docker.docker/Data/s51
com.docker.slirp is not running
[OK] moby-console
[OK] logs
[ERROR] vmnetd
/var/tmp/com.docker.vmnetd.socket does not exist
Unexpected error (No such file or directory) connecting to /var/tmp/com.docker.vmnetd.socket
/private/tmp/vmnetd/com.docker.vmnetd is not running
[OK] env
[ERROR] moby
/Users/rponte/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. Install Docker For Mac;
2. Run it;

The Kitematic link downloads a dmg. This dmg, when trying to open, states its damaged. I tried this more than once.

This has just started very recently (last ran Docker last week). Looks to be a duplicate of #42, although that issue is sparse of details.

Diagnostic ID: DEDC5D44-B2E1-4661-8003-309D06286A47
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[ERROR] docker-cli
/var/run/docker.sock does not exist
Permission denied (EACCES) connecting to /var/run/docker.sock: check permissions
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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. Running any docker commands in Terminal (e.g. docker info).
2. I've tried resetting and uninstalling using the Uninstall/Reset option in Preferences, then reinstalling using a fresh download. No luck.

Expected behavior

Not to see that Docker has been updated notification on every boot.

Actual behavior

Each time Docker for Mac starts I see the following notification.

Note: I switched from the Beta to Stable release using an in-place upgrade (e.g did not uninstall Docker for Mac before installing the stable package).

Information

Diagnostic ID: 794E1C65-4D46-447A-BD5E-297BC892F8A8
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. Quit Docker for Mac
2. Open Docker for Mac

Expected behavior

Actual behavior

Information

Diagnostic ID: 2EFD90F8-98C3-4386-90DA-44DE965DCB66
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.6 (Build 15G31)
[ERROR] docker-cli
/var/run/docker.sock does not exist
Unexpected error (No such file or directory) connecting to /var/run/docker.sock
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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

Docker for mac should resolve through VPN connection

Actual behavior

Docker seems oblivious to currently open VPN connection

Information

Diagnostic ID: BBD3F7BF-C35D-4FB9-AB04-80ADBD8DBB9B
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. Turn on docker for mac
2. Connect to vpn (I have tried reversing these first two steps)
3. Attempt to build image that requires resolution to domain inside of VPN

Example docker file:

FROM node:argon

RUN mkdir /srv/app
WORKDIR /srv/app
RUN npm set registry <internal vpn domain>
RUN npm install -g -q coffee-script grunt-cli

ADD . /srv/app
RUN npm install -q

RUN grunt
EXPOSE 3000

CMD ["npm", "start"]

1. echo "Asia/Shanghai" | sudo tee /etc/timezone
2. sudo docker run -d --restart=always --name rancher-server -p 8080:8080
   -v /etc/localtime:/etc/localtime:ro
   -v /etc/timezone:/etc/timezone:ro
   rancher/server:v1.0.1

docker: Error response from daemon: oci runtime error: rootfs_linux.go:53: mounting "/var/lib/docker/aufs/mnt/14fc257654604475143d99f76554a74c5affe82cfd66a96222780104a083fa9a/etc/timezone" to rootfs "/var/lib/docker/aufs/mnt/14fc257654604475143d99f76554a74c5affe82cfd66a96222780104a083fa9a" caused "not a directory".

docker info

Containers: 2
Running: 2
Paused: 0
Stopped: 0
Images: 97
Server Version: 1.12.0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 202
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: null host bridge overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.15-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 9.745 GiB
Name: moby
ID: NPHU:NER7:YRWZ:YGES:2V5M:GDT3:G67F:V3KK:2NMY:AUEQ:JRQ5:K2HV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 29
Goroutines: 44
System Time: 2016-08-01T07:50:37.620384403Z
EventsListeners: 1
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
127.0.0.0/8

Expected behavior

Docker should start up

Actual behavior

Docker is not starting up

Information

Diagnostic ID: 93EAC757-7A6D-41B0-ADF3-768A3AF9FDB9
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[ERROR] docker-cli
/var/run/docker.sock does not exist
Unexpected error (No such file or directory) connecting to /var/run/docker.sock
Connection refused (ECONNREFUSED) connecting to /Users/wombat/Library/Containers/com.docker.docker/Data/s60: check if service is running
docker ps failed
[OK] app
[OK] moby-syslog
[OK] disk
[OK] virtualization
[OK] system
[OK] menubar
[ERROR] osxfs
com.docker.osxfs is not running
[ERROR] db
Connection refused (ECONNREFUSED) connecting to /Users/wombat/Library/Containers/com.docker.docker/Data/s40: check if service is running
com.docker.db is not running
[ERROR] slirp
Connection refused (ECONNREFUSED) connecting to /Users/wombat/Library/Containers/com.docker.docker/Data/s51: check if service is running
com.docker.slirp is not running
[OK] moby-console
[OK] logs
[ERROR] vmnetd
Connection refused (ECONNREFUSED) connecting to /var/tmp/com.docker.vmnetd.socket: check if service is running
/private/tmp/vmnetd/com.docker.vmnetd is not running
[OK] env
[OK] moby
[ERROR] driver.amd64-linux
Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running

Steps to reproduce

I installed Docker for Mac 1.12 and Docker asked to install networking components - I then entered my password and Docker failed with the Diagnostics I mentioned

Expected behavior

Copying version or debug information from these 2 windows by pressing cmd + C for including that information in an issue for example.

Actual behavior

Nothing gets copied to the clipboard. The text is selectable, but not copyable.

Information

Diagnostic ID: D89032CA-B2D3-427F-8E06-66527CB81679
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce the behavior

1. Open About Docker or Diagnose and Feedback... from the Docker icon in the menu bar.
2. Try to copy some text from the windows, nothing gets copied into the clipboard.

Expected behavior

start the docker daemon

Actual behavior

unable to start the daemon. the docker icon showing on the top menu bar keeps flashing.

Information

Diagnostic ID: A218848E-23E3-48CD-A022-DDBD8B28D223
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.10.5 (Build 14F1909)
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. click the docker icon in the applications

Expected behavior

Start docker

Actual behavior

Docker does not start anymore. I used it for days, and now does not start:
it is in this status:

Information

Diagnostic ID: ABEA8DD3-0F1F-440B-9DD6-EB97931AF490
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.10.5 (Build 14F1605)
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

I am trying just to start it.
Thank you!

Expected behavior

Docker works properly

Actual behavior

Docker tries to start "forever" but nothing happens.

Information

Diagnostic ID: C2193A9E-94BC-4376-BE22-93666DE1E973
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.6 (Build 15G31)
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. Start Docker on Mac

Expected behavior

Quitting Docker from the menu bar kills all Docker processes.

Actual behavior

The com.docker.vmnetd process survives.

Information

Diagnostic ID: D89032CA-B2D3-427F-8E06-66527CB81679
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. Start Docker for Mac.
2. Quit Docker for Mac via the icon in the menu bar.
3. Check for running processes that have docker in the name.

Expected behavior

Actual behavior

Information

Diagnostic ID: 6C65A543-4C30-4C8D-8AFF-195FF9E218D8
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

I create a container (nginx) for test and the spawn a terminal for a CLI.
docker --version is OK ...
But when i run:

$: docker ps -a  15:18:09
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Seems that i can't find the socket of docker.
A ny idea where i can configure this ?

Another infos on docker process:

=== 8< =================================== >8 ===

ps -ef | grep -i docker  15:13:58
501 15479 1 0 2:37 ?? 0:13.08 /Applications/Docker.app/Contents/MacOS/Docker -psn_0_1401174
0 15496 1 0 2:38 ?? 0:00.01 /Library/PrivilegedHelperTools/com.docker.vmnetd
501 15504 15479 0 2:39 ?? 0:00.05 /Applications/Docker.app/Contents/MacOS/com.docker.osx.hyperkit.linux -watchdog fd:0
501 15506 15504 0 2:39 ?? 0:00.08 /Applications/Docker.app/Contents/MacOS/com.docker.osx.hyperkit.linux -watchdog fd:0
501 15507 15504 0 2:39 ?? 0:01.15 com.docker.db --url fd:3 --git /Users/mic/Library/Containers/com.docker.docker/Data/database
501 15508 15504 0 2:39 ?? 0:00.82 com.docker.osxfs --address fd:3 --connect /Users/mic/Library/Containers/com.docker.docker/Data/@connect --control fd:4 --volume-control fd:5 --database /Users/mic/Library/Containers/com.docker.docker/Data/s40
501 15509 15504 0 2:39 ?? 0:00.49 com.docker.slirp --db /Users/mic/Library/Containers/com.docker.docker/Data/s40 --ethernet fd:3 --port fd:4 --vsock-path /Users/mic/Library/Containers/com.docker.docker/Data/@connect --max-connections 900
501 15510 15504 0 2:39 ?? 0:00.41 com.docker.osx.hyperkit.linux
501 15511 15504 0 2:39 ?? 0:00.46 com.docker.driver.amd64-linux -db /Users/mic/Library/Containers/com.docker.docker/Data/s40 -osxfs-volume /Users/mic/Library/Containers/com.docker.docker/Data/s30 -slirp /Users/mic/Library/Containers/com.docker.docker/Data/s50 -vmnet /var/tmp/com.docker.vmnetd.socket -port /Users/mic/Library/Containers/com.docker.docker/Data/s51 -vsock /Users/mic/Library/Containers/com.docker.docker/Data -docker /Users/mic/Library/Containers/com.docker.docker/Data/s60 -addr fd:3 -debug
501 15512 15510 0 2:39 ?? 0:00.05 /Applications/Docker.app/Contents/MacOS/com.docker.osx.hyperkit.linux
501 15513 15511 0 2:39 ?? 0:00.04 /Applications/Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db /Users/mic/Library/Containers/com.docker.docker/Data/s40 -osxfs-volume /Users/mic/Library/Containers/com.docker.docker/Data/s30 -slirp /Users/mic/Library/Containers/com.docker.docker/Data/s50 -vmnet /var/tmp/com.docker.vmnetd.socket -port /Users/mic/Library/Containers/com.docker.docker/Data/s51 -vsock /Users/mic/Library/Containers/com.docker.docker/Data -docker /Users/mic/Library/Containers/com.docker.docker/Data/s60 -addr fd:3 -debug
501 15514 15511 0 2:39 ?? 0:18.94 /Applications/Docker.app/Contents/MacOS/com.docker.hyperkit -A -m 2G -c 4 -u -s 0:0,hostbridge -s 31,lpc -s 2:0,virtio-vpnkit,uuid=22fc5061-4e8d-4a2b-9692-92cd1754c495,path=/Users/mic/Library/Containers/com.docker.docker/Data/s50,macfile=/Users/mic/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/mac.0 -s 3,virtio-blk,file:///Users/mic/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2,format=qcow -s 4,virtio-9p,path=/Users/mic/Library/Containers/com.docker.docker/Data/s40,tag=db -s 5,virtio-rnd -s 6,virtio-9p,path=/Users/mic/Library/Containers/com.docker.docker/Data/s51,tag=port -s 7,virtio-sock,guest_cid=3,path=/Users/mic/Library/Containers/com.docker.docker/Data,guest_forwards=2376;1525 -l com1,autopty=/Users/mic/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty,log=/Users/mic/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/mic/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/hypervisor.pid
501 18656 15479 0 3:17 ?? 0:00.01 /Applications/Docker.app/Contents/Resources/bin/com.docker.frontend {"action":"vmstateevent","args":{"vmstate":"running"}}
501 18657 18656 0 3:17 ?? 0:00.01 /Applications/Docker.app/Contents/Resources/bin/com.docker.frontend {"action":"vmstateevent","args":{"vmstate":"running"}}
501 18659 17456 0 3:17 ttys002 0:00.00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn -i docker

=== 8< =================================== >8 ===

Thanks for the reply !

Rgds,

another info

Expected behavior

starts docker, run commands normally

Actual behavior

start docker, the whale lets run, and when I run docker ps, docker version, docker logs the following messages appear:

root# docker version
Client:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:15:28 2016
OS/Arch: darwin/amd64
Error response from daemon: dial unix /Users/claudio/Library/Containers/com.docker.docker/Data/*00000003.00000948: connect: no such file or directory

Information

in any command gives that error

Diagnostic ID: A60D01B2-A954-4454-9EBD-B1E37020C24F
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[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/claudio/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. only install & start docker stable and beta. mac os x 10.11.6 imac 14.2
2. docker is starting always

Expected behavior

Actual behavior

Information

Diagnostic ID: 5EDFA5D9-EF23-411C-BBEF-D265D91079B0
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.4 (Build 15E65)
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

First of all, thanks for bringing docker to the mac natively 🎉 It's been a huge help!

I have configured my Mac to resolve the .dev TLD to 127.0.0.1 following this tutorial. In summary, one installs and configures dnsmasq and then tells macOS' resolver to redirect all DNS queries for .dev to dnsmasq.

Expected behavior

host$: ping test.dev
64 bytes from 127.0.0.1: [...]

container$: ping test.dev
64 bytes from 127.0.0.1: [...]

Actual behavior

host$: ping test.dev
64 bytes from 127.0.0.1: [...]

container$: ping test.dev
64 bytes from 127.0.53.53: [...]

I'm not certain if this is the intended behavior, so my apologies if this is not a bug.

Information

• Apparently .dev domains (since they became a gTLD) currently always resolve to 127.0.53.53
• Diagnostic ID: 93B2DFC9-3227-4A5F-9240-4208C2618238
• This does not seem to be related to a single Docker file
• Tested on OSX 10.11.6, w/ both stable and beta channel

Steps to reproduce the behavior

1. Set up resolver to forward DNS queries for a specific TLD to a different DNS than the system's default
2. Start a docker container that has ping installed
3. ping inside the container will resolve differently from ping outside the container

Expected behavior

When the Mac wakes from sleep, the Moby VM should resync its local system time with the Mac's system time.

Actual behavior

Moby VM time simply resumes counting from the time the Mac went to sleep. This results in strange and many times difficult to troubleshoot issues with software running in containers.

Information

Docker for Mac: version: win-beta-v1.12.0-rc5-beta21-73-g9cd1dc2
OS X: version 10.11.6 (build: 15G31)
logs: /tmp/1D6BCF46-49C8-45BC-86AC-EF873AB86DFB/20160730-113336.tar.gz
[OK]     docker-cli
[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
[OK]     moby
[OK]     driver.amd64-linux

Steps to reproduce the behavior

1. put Mac to sleep, wait n seconds/minutes/hours
2. wake Mac from sleep
3. Issue date in container or Moby VM and see that it outputs $(date) - n

Expected behavior

I resumed my laptop after putting it to sleep and then tried running docker images. docker ps works fine but images just hangs. I believe the laptop went to sleep while it was still pulling down an image which led it to this state.

Actual behavior

docker images should show me my images and remove the undownloaded image that my laptop was retrieving before it went to sleep.

Information

Diagnostic ID: A64D5A2B-14F9-4BBC-81D6-03B2C8794F63
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[OK] app
[OK] moby-syslog
[ERROR] disk
disk check failed with: Failure("exec: /Applications/Docker.app/Contents/Resources/bin/../../../Contents/MacOS/qemu-img check /Users/yongshin/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 > /tmp/A64D5A2B-14F9-4BBC-81D6-03B2C8794F63/20160730-134655/qemu-img-check.stdout 2> /tmp/A64D5A2B-14F9-4BBC-81D6-03B2C8794F63/20160730-134655/qemu-img-check.stderr: exit 3")
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

docker ps should return immediately

Actual behavior

docker ps command hangs forever

Information

Diagnostic ID: F4F5D337-2486-44AE-B5B0-B7A76548E67B
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.4 (Build 15E65)
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. rebooted machine, still happens
2. reinstalled and rebooted, still happens

Works as expected on terminal
but try to run docker inside tmux

Expected behavior

docker ps -a
should be able to list the containers

Actual behavior

docker ps -a
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Information

Diagnostic ID: 53BCDA1D-FA89-4824-A4EC-1F5E8355FD5C
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.2 (Build 15C50)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. ...
2. ...

Expected behavior

$ docker pull busybox
Using default tag: latest
latest: Pulling from library/busybox
8ddc19f16526: Pull complete 
Digest: sha256:a59906e33509d14c036c8678d687bd4eec81ed7c4b8ce907b888c607f6a1e0e6
Status: Downloaded newer image for busybox:latest

Actual behavior

$ docker pull busybox
Using default tag: latest
Pulling repository docker.io/library/busybox
Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/busybox/images. You may want to check your internet connection or if you are behind a proxy.

Information

• Diagnostic ID: 41904CCA-8136-415B-978E-881FBECA4F19
• host distribution and version: 10.11.6 (15G31)

Steps to reproduce the behavior

1. (Using a host with IPv6 connectivity - this may work on a host without, I don't know)
2. System Preferences > Network > Advanced > DNS
3. Set the first DNS server in the list to 2001:4860:4860::8888 (these are Google's public DNS servers, I imagine the issue would present the same with any v6 servers)
4. Set the second DNS server to 2001:4860:4860::8844
5. Set the third DNS server in the list to 8.8.8.8
6. Press Ok
7. Press Apply
8. Run docker pull busybox

To not see this behaviour:

1. Move the v4 DNS server to the top of the list, or move it to the second place in the list
2. Press Ok
3. Press Apply
4. Run docker pull busybox

(As far as I can tell, Docker for Mac is only looking at the first two entries in /etc/resolv.conf then it gives up, and for whatever reason it has no access to the v6 internet)

This issue was previously discussed on the forums: https://forums.docker.com/t/error-network-timed-out-while-trying-to-connect-to-index-docker-io/17206

Expected behavior

Actual behavior

Information

Diagnostic ID: 9B084DE8-D300-4263-BEE1-3C0D6DB70A73
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.3 (Build 15D21)
[ERROR] docker-cli
wrong Docker version: 1.9.1 (expected 1.12.0)
/var/run/docker.sock does not exist
Unexpected error (No such file or directory) connecting to /var/run/docker.sock
/Users/knothpascal/Library/Containers/com.docker.docker/Data/s60 does not exist
Unexpected error (No such file or directory) connecting to /Users/knothpascal/Library/Containers/com.docker.docker/Data/s60
docker ps failed
[OK] app
[OK] moby-syslog
[ERROR] disk
disk check failed with: Failure("exec: /Applications/Docker.app/Contents/Resources/bin/../../../Contents/MacOS/qemu-img check /Users/knothpascal/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 > /tmp/9B084DE8-D300-4263-BEE1-3C0D6DB70A73/20160729-115839/qemu-img-check.stdout 2> /tmp/9B084DE8-D300-4263-BEE1-3C0D6DB70A73/20160729-115839/qemu-img-check.stderr: exit 1")
[OK] virtualization
[OK] system
[OK] menubar
[ERROR] osxfs
com.docker.osxfs is not running
[ERROR] db
/Users/knothpascal/Library/Containers/com.docker.docker/Data/s40 does not exist
Unexpected error (No such file or directory) connecting to /Users/knothpascal/Library/Containers/com.docker.docker/Data/s40
com.docker.db is not running
[ERROR] slirp
/Users/knothpascal/Library/Containers/com.docker.docker/Data/s51 does not exist
Unexpected error (No such file or directory) connecting to /Users/knothpascal/Library/Containers/com.docker.docker/Data/s51
com.docker.slirp is not running
[OK] moby-console
[OK] logs
[ERROR] vmnetd
/var/tmp/com.docker.vmnetd.socket does not exist
Unexpected error (No such file or directory) connecting to /var/tmp/com.docker.vmnetd.socket
/private/tmp/vmnetd/com.docker.vmnetd is not running
[OK] env
[ERROR] moby
/Users/knothpascal/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. ...

Expected behavior

$ ping -c 1 test.local
$ docker run -t alpine ping -c 1 test.local

Both commands should be able to ping the other device in local network.

Actual behavior

$ ping -c 1 test.local
PING test.local (192.168.X.XXX): 56 data bytes
64 bytes from 192.168.X.XXX: icmp_seq=0 ttl=64 time=3.543 ms

--- test.local ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 3.543/3.543/3.543/0.000 ms

$ docker run -t alpine ping -c 1 test.local
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
e110a4a17941: Pull complete 
Digest: sha256:3dcdb92d7432d56604d4545cbd324b14e647b313626d99b889d0626de158f73a
Status: Downloaded newer image for alpine:latest
ping: bad address 'test.local'

Information

Diagnostic ID: 5CEA5887-9236-445B-82C2-9A202A9DA0AA
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. Have a device running with avahi in your local network, eg. a Raspberry Pi with either Raspbian or HypriotOS
2. ping the device test with ping test.local
3. run the ping inside a container

$ docker run -t alpine ping -c 1 test.local
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
e110a4a17941: Pull complete 
Digest: sha256:3dcdb92d7432d56604d4545cbd324b14e647b313626d99b889d0626de158f73a
Status: Downloaded newer image for alpine:latest
ping: bad address 'test.local'

Yesterday I switch from a vmwarefusion docker machine to Docker for Mac and now this 😢 -- no problem 😆 Just starting to give feedback.

I just recreated a docker machine and tested if it worked previously. And yes using the name announced by avahi also works inside a container.

$ docker-machine create -d vmwarefusion --vmwarefusion-memory-size 2048 dev
$ eval $(docker-machine env dev)
$ docker run -t alpine ping -c 1 test.local
PING test.local (192.168.X.XXX): 56 data bytes
64 bytes from 192.168.X.XXX: seq=0 ttl=127 time=1.978 ms

--- test.local ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 1.978/1.978/1.978 ms

Expected behavior

Containers inside the VM are killed first, crucial services last. An error message that the VM hit an oom error and the allocated memory should be increased.

Actual behavior

transfused seems to be killed by the oom killer and the docker vm is restarting.

2016-07-29 17:09:06 +0000 UTC daemon.crit /sbin/transfused: /Users: error writing:
2016-07-29 17:09:06 +0000 UTC daemon.crit /sbin/transfused: Out of memory

Information

• 259D4E40-1478-48B5-B004-7E5688B30B30
• OS X 10.11.6 MacBook Pro (Retina, 13-inch, Early 2015)

Steps to reproduce the behavior

1. Consume more memory then the VM has configured
2. Docker VM is restarting without further notice

Expected behavior

Actual behavior

Information

Diagnostic ID: D5A3393D-36ED-457C-AD24-E37C701B8123
Docker for Mac: 1.12.0-beta21 (Build 10868)
macOS: Version 10.11.5 (Build 15F34)
[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
[OK] moby
[OK] driver.amd64-linux

Expected behavior

Docker keeps running the container

Actual behavior

Docker drops connection

Information

shortly after starting, docker loses connection to my container; worked pretty reliably until RC4 - did a timeout get lowered?

Diagnostic ID: 31B424D2-BFB3-47AF-AEB3-D8A375553650
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. build container with postgresql, nodejs, nginx, salt, python, rabbitmq
2. start and initialize...
   20160729-183534.tar.gz
   20160729-183602.tar.gz

Expected behavior

$ docker version

Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      darwin/amd64
Server:
...
...
...

Actual behavior

$ docker version

Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      darwin/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Information

Diagnostic ID: FF636554-6BF7-482D-9628-0F1D65FE333F
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. install docker for mac
2. run docker version

Is this issue related other softwares or services running on my machine?

Expected behavior

Docker commands (e.g. docker images, docker ps) should be working as expected.

Actual behavior

Docker commands error due to network issues.

$ docker images

An error occurred trying to connect: Get https://192.168.59.103:2376/v1.24/images/json: dial tcp 192.168.59.103:2376: getsockopt: network is unreachable

$ docker ps

An error occurred trying to connect: Get https://192.168.59.103:2376/v1.24/containers/json: dial tcp 192.168.59.103:2376: getsockopt: network is unreachable

Information

Diagnostic ID: B05ACE3C-2617-4A74-81F9-62001BFEE9BE
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.4 (Build 15E65)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. Install docker for mac.
2. Run any docker commands.

Expected behavior

It happened right after installation, it should open up the app but instead it opened a fatal error
window which said :
"Docker does not rely on Virtualbox but may not work properly on systems with VirtualBox versions prior to v4.3.30
VirtualBox v4.3.28 is currently installed.
Please upgrade or uninstall Virtualbox."

I uninstalled the virtualbox but it didn't make any difference

Information

Diagnostic ID: CF8ED858-FC2A-42E5-A548-C2C622BA2863
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.4 (Build 15E65)
[ERROR] docker-cli
cannot find docker
docker-cli check failed with: Failure("docker -v: timeout after 10.00s")
[OK] app
[OK] moby-syslog
[ERROR] disk
disk check failed with: Failure("exec: /Applications/Docker.app/Contents/Resources/bin/../../../Contents/MacOS/qemu-img check /Users/sahand/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 > /tmp/CF8ED858-FC2A-42E5-A548-C2C622BA2863/20160729-132918/qemu-img-check.stdout 2> /tmp/CF8ED858-FC2A-42E5-A548-C2C622BA2863/20160729-132918/qemu-img-check.stderr: exit 1")
[OK] virtualization
[OK] system
[OK] menubar
[ERROR] osxfs
com.docker.osxfs is not running
[ERROR] db
/Users/sahand/Library/Containers/com.docker.docker/Data/s40 does not exist
Unexpected error (No such file or directory) connecting to /Users/sahand/Library/Containers/com.docker.docker/Data/s40
com.docker.db is not running
[ERROR] slirp
/Users/sahand/Library/Containers/com.docker.docker/Data/s51 does not exist
Unexpected error (No such file or directory) connecting to /Users/sahand/Library/Containers/com.docker.docker/Data/s51
com.docker.slirp is not running
[OK] moby-console
[OK] logs
[ERROR] vmnetd
/var/tmp/com.docker.vmnetd.socket does not exist
Unexpected error (No such file or directory) connecting to /var/tmp/com.docker.vmnetd.socket
/private/tmp/vmnetd/com.docker.vmnetd is not running
[OK] env
[ERROR] moby
/Users/sahand/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. ...

Feature Request

Hi, I had a feature request I wondered if you would consider adding to Docker for Mac?

On the menubar icon, you have a 'restart' button displayed next to the status - I wondered if you could add 'start' and 'stop' buttons also? The reason being that sometimes I would like to stop the Docker virtual machine, but keep the menubar icon running so I can easily start the VM again.

It might also be useful to have the initial state configurable, so you decide whether the VM should be started straight away or not.

Expected behavior

When I try to interact with a dialog box it should stay put and be interactive.

Actual behavior

Under certain conditions, dialog boxes stay in inaccessible workspaces and don't respond to input.

Information

Diagnostic ID: 9BE8F762-EE93-4099-906F-7AA69C221050
Docker for Mac: 1.12.0 (Build 10871)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[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
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. If I open a dialog box (Preferences, for example) while in a full screen workspace, I get switched to the desktop workspace, but the dialog box stays in the other workspace.
2. If I switch back to the workspace with the dialog box and try to click on it, I get switched back to the desktop workspace again.
3. If I switch back to the workspace with the dialog box, make the underlying application not fullscreen, then the Docker dialog box moves to the desktop workspace, but I still cannot interact with it. I can't even close the dialog box or access the Docker quit menu at that point.