This does NOT happen when using dlite and the same docker-compose file.
Information
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta10
Running diagnostic tests:
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160510-070336.tar.gz
Most specific failure is: No error was detected
Your unique id is: CE37C996-F318-47DE-B2CA-61AAD8A00AE4
Please quote this in all correspondence.
I Have the same problem, the com.docker.xhyve process stay on 70%, but when i access the container, in my case it is a PHP Application, on HTTP port, the CPU goes high like in the picture bellow.
OS Version: OS X El Capitan. 10.11.4
Docker version: 1.11.1-Beta10 (build: 6662)
Using 13 containers at same time.
mysql, mongo, rabbitmq, redis, dnsmasq, elasticsearch, consul, php, registrator, nginx, haproxy x 2 and varnish.
Bump? Any updates to the performance issues? They still exist with beta18.
My idle python container is using up more CPU than my Windows 10 virtual machine. I believe it’s filesystem related - the python development server constantly watches the filesystem for sourcecode changes, and I think this is where the issue lies.