suhanovv
April 29, 2016, 7:41pm
1
After starting container for Django with big code base:
version: '2'
services:
python:
build: ./python/
command: python manage.py runserver 0.0.0.0:8000
volumes:
- ../src/django:/code
links:
- memcached:memcached-01.mydomain.com
ports:
- "8000:8000"
environment:
- DJANGO_SETTINGS_MODULE=settings.local
processes com.docker.xhyve and com.docker.osxfs begin to use 90-180% CPU and 50-120% CPU
For hello world project from Django samples | Docker Docs CPU usage 5-10%
It appeared after the update to beta9 (build: 6388)
OS X: version 10.11.4 (build: 15E65)
4 Likes
savruk
May 4, 2016, 11:02pm
2
I have the same issue.
Running the server with --noreload option has lowered constant CPU usage from 90% to 5-6%. But that, obviously, didn’t help the spikes on request. Every request causes the CPU going high to 120-130%(sometimes even higher). After the request is served, everything goes back to normal.
abdul
May 5, 2016, 7:37am
3
This is what I noticed, and I have now temporarily stopped using “Docker for Mac - Beta”. There was a time when com.docker.xhyve was taking more 200% of CPU usage.
1 Like
This is what I get. On my ubuntu virtual machine (on vmware fusion), the same docker containers (3 of them linked via docker-compose) is consuming cpu as much as mac version.
1 Like
alfredb
May 8, 2016, 8:55am
5
Exaclty the same here, with no containers running. This happened when coming out of hibernation and lasted for a couple of minutes before going back to normal. The computer was very sluggish during that time. I also had a virtualbox VM running (which didn’t experience any issues). I’m on a MacBook Air (13-inch, Early 2015), 2,2 GHz Intel Core i7, 8 GB 1600 MHz DDR3.
1 Like
Ditto. Seems to coincide with my macbook waking up from sleep
Happens regardless of whether I have any local containers running
Issue type Bug?
Sorry. I’d post more precise OS and App version but I’m using a diff macbook right now #firstworldproblems
1 Like
rshmelev
May 9, 2016, 12:59pm
7
beta10, build 6662, Yosemite,
1 Like
dsheets
May 9, 2016, 1:04pm
8
Could someone who has experienced this please run pinata diagnose -u and post the result here? Also, the approximate wall-clock time of the occurrence would help correlate the behavior to the logs. In particular, it is possible that after sleep there are processes in the VM that cause a “log storm” which cause the VM and file system to run hot until the logging of messages regarding the sleep/wake/clock skew has passed.
Thanks,
David
rygwdn
May 9, 2016, 2:41pm
9
I have the same issues here using Django with auto-reload turned on. Looks like the CPU usage spikes every time python runs through the list of files and stats them. The CPU usage reported by docker stats is minimal (usually less than 1%) but Activity Monitor is reporting over 100%. Also doesn’t look like I’m able to get inotify events so I can’t use that instead…
I am also seeing this when my Macbook Pro wakes from sleep (Edit: nothing related to osxfuse though, it’s just xhyve misbehaving. Also not running django). CPU usage of com.docker.xhyve pegs at 295-300% in Activity Monitor (I have 3 cores allocated to the VM) and remains there until I force the VM to restart. I ran the Pinata output:
~/ pinata diagnose -u OS X: version 10.10.5 (build: 14F1713) Docker.app: version v1.11.1-beta10 Running diagnostic tests: Error docker ps: timeout after 10.00s Thread 6 killed on uncaught exception Misc.Failure Error docker ps: timeout after 10.00s [ERROR] docker-cli docker ps failed: Misc.Failure [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 Error echo "00000003.0000f3a6" | nc -U /var/tmp/com.docker.vsock/connect > /tmp/20160509-110040/diagnostics.tar: timeout after 30.00s Docker logs are being collected into /tmp/20160509-110040.tar.gz Most specific failure is: docker ps failed: Misc.Failure Your unique id is: DAB18839-2998-4C8B-9097-69741B1C404F Please quote this in all correspondence.
1 Like
chapati
May 9, 2016, 3:08pm
11
same issue. pinata id: FAD6A9DD-FB46-4E55-881D-84A9C2D27B6C
Hi, same problem here: i’m running docker-compose with a mounted app directory on a gulp project. The file watching process is incredibly slow and CPU usage goes up to 250% and more.
You can find my logs from “pinata diagnose -u” here:https://dl.dropboxusercontent.com/u/8976594/20160509-231144.tar.gz
The docker compose file:https://dl.dropboxusercontent.com/u/8976594/docker-compose.yml
Hopefully this can be fixed soon as we are forced to use virtualbox again…
1 Like
patricknw
May 10, 2016, 12:07am
13
Ditto. Machine started heating up and the fan got loud this morning shortly after waking. Quitting the app fixed the issue, and it did not reappear upon re-launch.
Version 1.11.1-beta10 (build: 6662)
1 Like
drben
May 10, 2016, 1:33am
14
tyr:~ benc$ uname -a
It appears to be sleep related, here is the console.app info, I quit it while logging, no containers running, 2 CPUs, ans 2GB of RAM
5/9/16 7:04:02.400 PM Docker[40036] System wants to go to sleep
drben
May 10, 2016, 1:37am
15
Process: com.docker.xhyve [40038]
Call graph:com.apple.AE (681.5 - 681.7) <2BF39455-1CDD-392C-824A-9972C6B1FB57> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
abdul
May 10, 2016, 11:03am
16
@elmarputz : Did you examine what’s in logs? There are things that shouldn’t be there. Hardware serial numbers, all processes, and lot more. I have created another thread to question their motive to collect so much.
You should examine before you upload, you never know what you might end up exposing
Thanks
elmarputz
May 10, 2016, 11:05am
17
Hi,
thanks for the info - as I did remove the files immediately after I got the
bwvr
May 10, 2016, 11:47am
18
Hi, I just started docker beta last night. This morning, I saw high CPU usage (200%) even though I don’t have any containers running. Waking up from sleep seems like the steps to reproduce.
OS X 10.10.5
Using the docker command from CLI was unresponsive (e.g. running docker ps just hangs). Resolution was to Quit Docker.
1 Like
nkobber
May 10, 2016, 8:47pm
19
Ran the diagnose while com.docker.hyperkit was at about 300% cpu and com.docker.osxfs was about 125% cpu.
$ pinata diagnose -u OS X: version 10.11.4 (build: 15E65) Docker.app: version v1.11.1-beta11 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-224447.tar.gz Most specific failure is: No error was detected Your unique id is: 444B1E2E-6FF7-4689-97F6-F227C31A4469 Please quote this in all correspondence.
shito
May 13, 2016, 8:17am
21
I have the same problem, but instead of com.docker.xhyve, it’s com.docker.hyperkit - just running an alpine with drupal8 the cpu usage is getting up to 160%.
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta11
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/20160513-101040.tar.gz
Most specific failure is: No error was detected
Your unique id is: 03E4893C-1D2F-41E9-9B03-0B3F2DECB914
