docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.43k stars 117 forks source link

Docker for Mac repeatable crashing #1020

Closed philjones88 closed 7 years ago

philjones88 commented 7 years ago

Expected behavior

To not crash. Running SeleniumHQ selenium-hub and node-chrome-debug images.

https://github.com/SeleniumHQ/docker-selenium

Actual behavior

Crashes.

Information

Hardware Overview:

  Model Name:   MacBook Pro
  Model Identifier: MacBookPro11,3
  Processor Name:   Intel Core i7
  Processor Speed:  2.6 GHz
  Number of Processors: 1
  Total Number of Cores:    4
  L2 Cache (per Core):  256 KB
  L3 Cache: 6 MB
  Memory:   16 GB
  Boot ROM Version: MBP112.0138.B17
  SMC Version (system): 2.19f12
  Serial Number (system):   C02LK0NBFR1M
  Hardware UUID:    4E64AB12-2CB3-5CAF-927A-F4CC82287AEE
System Software Overview:

  System Version:   macOS 10.12.1 (16B2657)
  Kernel Version:   Darwin 16.1.0
  Boot Volume:  Macintosh HD
  Boot Mode:    Normal
  Computer Name:    Phil’s MacBook Pro
  User Name:    Phil Jones (phil)
  Secure Virtual Memory:    Enabled
  System Integrity Protection:  Enabled
  Time since boot:  7:26

B61E99DF-82FC-4705-93F7-D5CBE45C367D

Docker for Mac: version: 1.13.0-rc2-beta31 (de6f6c2)
OS X: version 10.12.1 (build: 16B2657)
logs: /tmp/B61E99DF-82FC-4705-93F7-D5CBE45C367D/20161207-145750.tar.gz
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     db
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     slirp
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     menubar
[OK]     disk
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: vm exit[2]
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>:   reason      VMX
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: virtio-net-vpnkit: initialising, opts="uuid=d64cd55a-a1f6-4b54-b4dc-cd318de5edbc,path=/Users/phil/Library/Containers/com.docker.docker/Data/s50,macfile=/Users/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/mac.0"
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>:   rip     0xffffffff8183b9fd
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: Interface will have uuid d64cd55a-a1f6-4b54-b4dc-cd318de5edbc
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>:   inst_length 5
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: Connection established with MAC=c0:ff:ee:c0:ff:ee and MTU 1500
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>:   status      0
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: virtio-9p: initialising path=/Users/phil/Library/Containers/com.docker.docker/Data/s40,tag=db
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>:   exit_reason 2
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: virtio-9p: initialising path=/Users/phil/Library/Containers/com.docker.docker/Data/s51,tag=port
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>:   qualification   0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: linkname /Users/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>:   inst_type       0
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: COM1 connected to /dev/ttys000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>:   inst_error      0
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: COM1 linked to /Users/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_PIN_BASED_CTLS:           0x000000000000003f
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_PRI_PROC_BASED_CTLS:      0x00000000b5186dfa
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_SEC_PROC_BASED_CTLS:      0x00000000000000aa
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_ENTRY_CTLS:               0x00000000000093ff
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_EXCEPTION_BITMAP:         0x0000000000040000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_CR0_MASK:                 0x00000000e0000031
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_CR0_SHADOW:               0x0000000080050033
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_CR4_MASK:                 0x0000000000002000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_CR4_SHADOW:               0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_CS_SELECTOR:        0x0000000000000010
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_CS_LIMIT:           0x00000000ffffffff
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_CS_ACCESS_RIGHTS:   0x000000000000a09b
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_CS_BASE:            0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_DS_SELECTOR:        0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_DS_LIMIT:           0x00000000ffffffff
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_DS_ACCESS_RIGHTS:   0x000000000001c000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_DS_BASE:            0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_ES_SELECTOR:        0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_ES_LIMIT:           0x00000000ffffffff
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_ES_ACCESS_RIGHTS:   0x000000000001c000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_ES_BASE:            0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_FS_SELECTOR:        0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_FS_LIMIT:           0x00000000ffffffff
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_FS_ACCESS_RIGHTS:   0x000000000001c000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_FS_BASE:            0x00007fc167f98a80
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17850] <Error>: Socket.Stream: caught socket is not connected
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_GS_SELECTOR:        0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_GS_LIMIT:           0x00000000ffffffff
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_GS_ACCESS_RIGHTS:   0x000000000001c000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_GS_BASE:            0xffff88013fd00000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_SS_SELECTOR:        0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_SS_LIMIT:           0x00000000ffffffff
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17849] <Error>: Fatal unexpected exception: Socket.Closed
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_SS_ACCESS_RIGHTS:   0x000000000001c000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_SS_BASE:            0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_LDTR_SELECTOR:      0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_LDTR_LIMIT:         0x00000000ffffffff
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_LDTR_ACCESS_RIGHTS: 0x000000000001c000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_LDTR_BASE:          0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_TR_SELECTOR:        0x0000000000000040
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_TR_LIMIT:           0x0000000000002087
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_TR_ACCESS_RIGHTS:   0x000000000000008b
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_TR_BASE:            0xffff88013fd16040
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_GDTR_LIMIT:         0x000000000000007f
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_GDTR_BASE:          0xffff88013fd09000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_IDTR_LIMIT:         0x00000000ffffffff
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_IDTR_BASE:          0x0000000000000000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_CR0:                0x0000000080050033
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_CR3:                0x000000010e8b7000
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_CR4:                0x00000000000426a0
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: VMCS_GUEST_IA32_EFER:          0x0000000000000d01
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>:
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: rip: 0xffffffff8183b9fd rfl: 0x0000000000010087 cr2: 0xffff88013fd04ff8
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: rax: 0x0000000000000000 rbx: 0xffff88010e8670a8 rcx: 0x000000000000000b rdx: 0xffffffff810f825a
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: rsi: 0x000000000000000e rdi: 0xffffffff810f825a rbp: 0x000000000000000e rsp: 0xffff88010e866f88
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: r8:  0x0000000000030001 r9:  0x00000000ffffffff r10: 0x00007ffee501f418 r11: 0x0000000000000206
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17851] <Notice>: r12: 0xffff88010e8670a8 r13: 0xffff88010e8670a8 r14: 0x000000000000000b r15: 0x0000000000030001
Dec  7 15:14:25 Phils-MacBook-Pro Docker[557] <Notice>: Reap com.docker.osxfs (pid 17849): exit status 1
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17850] <Error>: Socket.Stream: caught connection refused
Dec  7 15:14:25 Phils-MacBook-Pro Docker[562] <Notice>: VM shutdown at 2016-12-07 15:14:25 +0000 GMT
Dec  7 15:14:25 Phils-MacBook-Pro Docker[557] <Notice>: Reap com.docker.driver.amd64-linux (pid 17851): exit status 0
Dec  7 15:14:25 Phils-MacBook-Pro Docker[17850] <Error>: Socket.Stream: caught connection refused
--- last message repeated 55 times ---
Dec  7 15:14:26 Phils-MacBook-Pro Docker[557] <Notice>: Stop 1 children with order 1: com.docker.driver.amd64-linux (pid 17851)
Dec  7 15:14:26 Phils-MacBook-Pro Docker[557] <Notice>: Stop 2 children with order 2: com.docker.osxfs (pid 17849), com.docker.slirp (pid 17850)
Dec  7 15:14:26 Phils-MacBook-Pro Docker[557] <Notice>: Signal terminated to com.docker.slirp (pid 17850)
Dec  7 15:14:26 Phils-MacBook-Pro Docker[557] <Notice>: Reap com.docker.slirp (pid 17850): signal: terminated
Dec  7 15:14:26 Phils-MacBook-Pro Docker[557] <Notice>: Starting com.docker.osxfs, com.docker.slirp, com.docker.driver.amd64-linux
Dec  7 15:14:26 Phils-MacBook-Pro Docker[557] <Notice>: Start com.docker.osxfs (pid 18938)
Dec  7 15:14:26 Phils-MacBook-Pro Docker[557] <Notice>: Start com.docker.slirp (pid 18939)
Dec  7 15:14:27 Phils-MacBook-Pro Docker[557] <Notice>: Start com.docker.driver.amd64-linux (pid 18940)
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: Acquired hypervisor lock
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18938] <Notice>: Logging to Apple System Log
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: Docker is not responding: Get http://./info: dial unix /Users/phil/Library/Containers/com.docker.docker/Data/*00000003.00000948: connect: connection refused: waiting 0.5s
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: OSX version = 10.12.1, default value of on-sleep = no not freeze
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: Logging to Apple System Log
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: Setting handler to ignore all SIGPIPE signals
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: vpnkit version d6831379839b1a74a6bc157e53bb3af124e01259 with hostnet version   uwt version 0.0.3 hvsock version 0.11.1
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: starting port forwarding server on port_control_url:fd:4 vsock_path:/Users/phil/Library/Containers/com.docker.docker/Data/@connect
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: Add(2): DNS configuration changed to: nameserver 81.91.102.37#53
    order 0
    nameserver 81.91.102.36#53
    order 0
    search vqcomms.com
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: hosts file has bindings for remote.vqcomms.com localhost broadcasthost localhost nas-server.local 192.150.14.69 192.150.18.101 192.150.18.108 192.150.22.40 192.150.8.100 192.150.8.118 209-34-83-73.ood.opsource.net 3dns-1.adobe.com 3dns-2.adobe.com 3dns-2.adobe.com 3dns-3.adobe.com 3dns-3.adobe.com 3dns-4.adobe.com 3dns.adobe.com activate-sea.adobe.com activate-sea.adobe.com activate-sjc0.adobe.com activate-sjc0.adobe.com activate.adobe.com activate.adobe.com activate.wip.adobe.com activate.wip1.adobe.com activate.wip2.adobe.com activate.wip3.adobe.com activate.wip3.adobe.com activate.wip4.adobe.com adobe-dns-1.adobe.com adobe-dns-2.adobe.com adobe-dns-2.adobe.com adobe-dns-3.adobe.com adobe-dns-3.adobe.com adobe-dns-4.adobe.com adobe-dns.adobe.com adobe-dns.adobe.com adobe.activate.com adobeereg.com crl.verisign.net CRL.VERISIGN.NET.* ereg.adobe.com ereg.adobe.com ereg.wip.adobe.com ereg.wip1.adobe.com ereg.wip2.adobe.com ereg.wip3.adobe.com ereg.wip3.adobe.com ereg.wip4.adobe.com hl2rcv.adobe.com ood.opsource.net practivate.adobe practivate.adobe.* practivate.adobe.com practivate.adobe.com practivate.adobe.ipp practivate.adobe.newoa practivate.adobe.ntp tss-geotrust-crl.thawte.com wip.adobe.com wip1.adobe.com wip2.adobe.com wip3.adobe.com wip3.adobe.com wip4.adobe.com wwis-dubc1-vip60.adobe.com wwis-dubc1-vip60.adobe.com wwis-dubc1-vip60.adobe.com
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: hypervisor: native
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: filesystem: osxfs
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: network: hybrid
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18938] <Notice>: Using protocol TwoThousand msize 16384
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: Hypervisor: native; BootProtocol: direct; UefiBootDisk: /Users/phil/UefiBoot.qcow2
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: Syslog socket is /Users/phil/Library/Containers/com.docker.docker/Data/*00000002.00000202
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: Logfile is /Users/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/syslog
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: Launched[18945]: /Applications/Docker.app/Contents/MacOS/com.docker.hyperkit -A -m 4G -c 4 -u -s 0:0,hostbridge -s 31,lpc -s 2:0,virtio-vpnkit,uuid=d64cd55a-a1f6-4b54-b4dc-cd318de5edbc,path=/Users/phil/Library/Containers/com.docker.docker/Data/s50,macfile=/Users/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/mac.0 -s 3,virtio-blk,file:///Users/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2?sync=1&buffered=1,format=qcow -s 4,virtio-9p,path=/Users/phil/Library/Containers/com.docker.docker/Data/s40,tag=db -s 5,virtio-rnd -s 6,virtio-9p,path=/Users/phil/Library/Containers/com.docker.docker/Data/s51,tag=port -s 7,virtio-sock,guest_cid=3,path=/Users/phil/Library/Containers/com.docker.docker/Data,guest_forwards=2376;1525 -l com1,autopty=/Users/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty,log=/Users/phil/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/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/hypervisor.pid
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: SC database lists search domains: vqcomms.com
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: SC database includes DNS service: { Addresses: 81.91.102.36, 81.91.102.37; Order: 0; Zones:  }
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: SC database has domain name:
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: attempting to reconnect to database
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: reconnected transport layer
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: updating connection limit to 900
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: allowing binds to any IP addresses
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: updating resolvers to nameserver 81.91.102.37#53
    timeout 2000
    order 0
    nameserver 81.91.102.36#53
    timeout 2000
    order 0
    search vqcomms.com
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: Add(3): DNS configuration changed to: nameserver 81.91.102.37#53
    timeout 2000
    order 0
    nameserver 81.91.102.36#53
    timeout 2000
    order 0
    search vqcomms.com
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: Creating slirp server pcap_settings:disabled peer_ip:192.168.65.2 local_ip:192.168.65.1 domain_search:vqcomms.com
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: PPP.negotiate: received ((magic VMN3T)(version 1)(commit de6f6c2e8d5ff4561b88bc212b9e2833b8684e4c))
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: TCP/IP ready
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: virtio-net-vpnkit: magic=VMN3T version=1 commit=0123456789012345678901234567890123456789
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: stack connected
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: starting introspection server on: fd:5
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18939] <Notice>: starting diagnostics server on: fd:6
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: mirage_block_open: file:///Users/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2?sync=1&buffered=1
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: mirage_block_open: file:///Users/phil/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2?sync=1&buffered=1 returning 0
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: mirage_block_stat
Dec  7 15:14:27 Phils-MacBook-Pro Docker[18940] <Notice>: vsock init 7:0 = /Users/phil/Library/Containers/com.docker.docker/Data, guest_cid = 00000003
Dec  7 15:14:29 Phils-MacBook-Pro Docker[18940] <Notice>:
    rdmsr to register 0x34 on vcpu 0
Dec  7 15:14:30 Phils-MacBook-Pro Docker[18940] <Notice>: Docker is not responding: Get http://./info: EOF: waiting 0.5s
--- last message repeated 1 time ---
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18939] <Notice>: BOOTREQUEST from c0:ff:ee:c0:ff:ee
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18939] <Notice>: BOOTREPLY to c0:ff:ee:c0:ff:ee yiddr 192.168.65.2 siddr 192.168.65.1 dns 192.168.65.1 router 192.168.65.1 domain
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: transfused: mount /bin/fusermount -o allow_other,max_read=1048576,subtype=osxfs /Users
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: transfused: mount /bin/fusermount -o allow_other,max_read=1048576,subtype=osxfs /Volumes
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: transfused: mount /bin/fusermount -o allow_other,max_read=1048576,subtype=osxfs /private
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: transfused: mount /bin/fusermount -o allow_other,max_read=1048576,subtype=osxfs /tmp
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: transfused: mount /bin/fusermount -o allow_other,max_read=1048576,subtype=osxfs /vq
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: transfused: mount /bin/fusermount -o allow_other,max_read=1048576,subtype=osxfs /host_docker_app
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: Negotiated transfuse notification channel for /Users
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: Negotiated transfuse notification channel for /Volumes
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: Negotiated transfuse notification channel for /private
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: Negotiated transfuse notification channel for /tmp
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: Negotiated transfuse notification channel for /vq
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: Negotiated transfuse notification channel for /host_docker_app
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18938] <Notice>: sending continue to client
Dec  7 15:14:37 Phils-MacBook-Pro Docker[18939] <Notice>: Using protocol TwoThousand msize 8192
Dec  7 15:14:42 Phils-MacBook-Pro Docker[18940] <Notice>: Docker is responding
Dec  7 15:14:42 Phils-MacBook-Pro Docker[562] <Notice>: VM started at 2016-12-07 15:14:42 +0000 GMT

Compose file:

version: '2'

services:
    selenium_hub:
        image: selenium/hub:3.0.1-aluminum
        container_name: selenium_hub
        privileged: true
        ports:
            - 4444:4444
        environment:
            - GRID_TIMEOUT=120000
            - GRID_BROWSER_TIMEOUT=120000
        networks:
            - selenium_grid_internal

    nodechrome:
        image: selenium/node-chrome-debug:3.0.1-aluminum
        privileged: true
        depends_on:
            - selenium_hub
        ports:
            - 5900
        environment:
            - no_proxy=localhost
            - TZ=Europe/London
            - HUB_PORT_4444_TCP_ADDR=selenium_hub
            - HUB_PORT_4444_TCP_PORT=4444
        networks:
            - selenium_grid_internal

networks:
    selenium_grid_internal:

docker-compose up -d

Run something that uses a selenium grid. Protractor etc.

Steps to reproduce the behavior

See above.

rogaha commented 7 years ago

@philjones88 I wasn't able to replicate your issue. I'm using the latest beta version (beta32). See below my environment details:

docker-compose.yml

version: '2'

services:
    nodejs:
        container_name: nodejs
        image: node:4
        ports:
            - "9001:9000"
        volumes:
            - ./:/tests
        working_dir: /tests
        depends_on:
            - selenium_hub
            - nodechrome
        command: "node /tests/node_modules/protractor/bin/protractor /tests/conf.js"
        networks:
            - selenium_grid_internal

    selenium_hub:
        image: selenium/hub:3.0.1-aluminum
        container_name: selenium_hub
        privileged: true
        ports:
            - 4444:4444
        environment:
            - GRID_TIMEOUT=120000
            - GRID_BROWSER_TIMEOUT=120000
        networks:
            - selenium_grid_internal

    nodechrome:
        image: selenium/node-chrome-debug:3.0.1-aluminum
        privileged: true
        depends_on:
            - selenium_hub
        ports:
            - 5900
        environment:
            - no_proxy=localhost
            - TZ=Europe/London
            - HUB_PORT_4444_TCP_ADDR=selenium_hub
            - HUB_PORT_4444_TCP_PORT=4444
        networks:
            - selenium_grid_internal

networks:
    selenium_grid_internal:

config.js

// An example configuration file.
exports.config = {
    seleniumAddress: 'http://selenium_hub:4444/wd/hub',
    // Capabilities to be passed to the webdriver instance.
    capabilities: {
        'browserName': 'chrome'
    },

    // Framework to use. Jasmine is recommended.
    framework: 'jasmine',

    // Spec patterns are relative to the current working directory when
    // protractor is called.
    specs: ['example_spec.js'],

    // Options to be passed to Jasmine.
    jasmineNodeOpts: {
        defaultTimeoutInterval: 30000
    }
};

package.json

{
  "dependencies": {
    "protractor": "*"
  },
  "scripts": {},
  "devDependencies": {
    "protractor": "*"
  }
}

Can you please try it again with that?

philjones88 commented 7 years ago

I should add it can happen after 1 suite of tests, even 1 test.

I'm on vacation at the moment but when I return next week I will try your docker file.

I've just upgraded to beta 32, the report was filed under beta 31, so fingers crossed it was magically fixed.

balrajsingh commented 7 years ago

This issue has been inactive for more than 14 days while marked as status/0-more-info-needed. It is being closed due to abandonment. Please feel free to re-open with more information about the problem.

MORE_INFO_EXPIRY_TIMEOUT

asprega commented 7 years ago

@philjones88 Hi, sorry to comment on a closed issue but I don't know how else to contact you. Have you been able to solve your issue? I have the same exact problem (same stacktrace), happens only with containerized chrome (either with selenium, or native chromedriver+chrome or chromium). Firefox runs perfectly. I tried switching back from edge to 17.03-ce stable, same result. My VM has always worked with 3GB of ram but the memory usage doesn't seem to be an issue: I increased it to 8GB and I get the same crash at mostly the same time.

philjones88 commented 7 years ago

@asprega sorry, I never really resolved it, just swapped to Protractor's web driver manager stuff instead which doesn't use docker :(

docker-robott commented 4 years ago

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