-
Notifications
You must be signed in to change notification settings - Fork 135
Closed
Description
Expected behaviour
If enough memory is available, starting Parallels Desktop should not impact Docker performances
Actual behaviour
Starting Parallels Desktop while Docker is running seems to make Docker even much slower than it is usually.
Information
- Full output of the diagnostics from "Diagnose & Feedback" in the menu
Docker 1.12.3-beta29.2
OS X: version 10.12.1 (build: 16B2555)
logs: /tmp/D71F5326-0D23-4376-8A06-67DBD61AF38C/20161103-185130.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
Failure: Could not upload diagnostic data to remote server (docker-diagnose exit code is 1)
Attached manually:
20161103-185130.tar.gz
Steps to reproduce the behavior
- start a very long build (for example GNU ARM Eclipse QEMU is notably long)
- start a Parallels virtual machine
- stop the Parallels VM
The curious thing is that even if Parallels is closed, the Docker speed remains low.