This image consists of SQL Server running on Linux based on Ubuntu 16.04. It can be used with the Docker Engine 1.8+ on Linux or on Docker for Mac/Windows. Expected behavior docker-compose ps and the rest of docker-compose commands should run reasonably fast. Free speech recognition software for mac. Actual behavior docker-compose ps takes 10 seconds. The rest of the commands run very slow as well. $ time docker-compose ps Name Command State Ports ------------------------------ real 0m10.318s user 0m0.238s sys 0m0.056s docker run ubuntu echo hello takes less then a second, while equivalent task in docker-compose.yml version: '3' services: ubuntu: image: ubuntu command: ['echo', 'hello'] takes 1 minute 16 seconds. Information • Full output of the diagnostics from 'Diagnose & Feedback' in the menu (b18e2a50c) macOS: version 10.12.4 (build: 16E195) logs: /tmp/E82DCC22-339C-4F85-B804-8DD9297FA7F3/20108.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 Steps to reproduce the behavior It used to work normal, then for no particular reason it started to run that slow. Resetting docker for mac to factory defaults, restarting OS doesn't help. So I have no idea how to reproduce this problem, as soon as I did nothing special. I am having this problem as well; here's a minimal working example. With this docker-compose.yml file: version: '2.1' services: ubuntu: image: ubuntu I get the following timings for container creation/running /bin/true. Note that I've run the docker-compose run step multiple times, so this doesn't even include things like network creation. $ time docker-compose run ubuntu true real 1m38.009s user 0m1.103s sys 0m0.260s Compare this with docker run: $ time docker run -ti ubuntu true real 0m0.851s user 0m0.021s sys 0m0.036s Anecdotally, the 1m38s time is very stable, and I suspect some kind of internal timeout occurring, especially as there is no high CPU utilization or anything like that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |