Running a command in a container pegs CPU at 200%

Expected behavior

Runs the google app engine python server within the container

Actual behavior

Gets half way through running of python server then hangs, pegs host CPU at 200%


» pinata diagnose -u [17:36:58]
OS X: version 10.11.5 (build: 15F34) version: v1.11.1-beta14.5.m
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/20160609-173658.tar.gz
Most specific failure is: No error was detected
Your unique id is: E6319CF8-0CB1-4BF1-B53B-06E0BA575DAC

  • a reproducible case if this is a bug, Dockerfiles FTW
    I cant reproduce this issue in a colleagues machine. It only hangs at 200% on my machine.

  • page URL if this is a docs issue or the name of a man page

Steps to reproduce the behavior

docker run --rm -ti -v ~/scratch/dugout-web:/src google/cloud-sdk
cd /src .
INFO 2016-06-09 16:38:54,666] Skipping SDK update check.
WARNING 2016-06-09 16:38:54,758] Could not read search indexes from /tmp/appengine.dugoutfc-web.root/search_indexes
INFO 2016-06-09 16:38:54,761] Starting API server at: http://localhost:45199

Then the server hangs. It should start up a dev server on port 8080. Docker CPU is 200%. Have tried factory resetting docker but still getting the issue.

Any ideas? Any way I can get more diagnostic logging from docker?