compose: Docker-compose run significantly slower than docker run

I have docker-compose 1.7 on Mac OSX. I figured out that it comes (in my case) from my home network, but I cannot find why:

• docker-compose up take ages to run
• shut down my wifi
• docker-compose up is REALLY fast
• now I can re-enable my wifi

So it clearly comes from my home network, as I cannot reproduce it from work network. But what is happening there…

The previous version of the beta docker for Mac OS also had problems with my network (could not pull any images), but since the last update of the beta, no issue anymore. I don’t know if this is related or not, just giving everything I observed.

I was blaming docker lately for being so slow for running phpunit, but tested it without docker-compose and was blazing fast, docker-compose is not usable for running tests, it takes more time for the container to actually run than the time needed for the tests. This needs to be fixed.

Any suggestions in 2019 regarding how to run the tests without the very slow setup of docker-compose?

Same issue on my Raspberry Pi 3 using Raspbian. Even on simple commands like showing the version, where not much work should be done, I got very slow responsiness:

pi@pi3:~ $ time docker --version
Docker version 17.09.0-ce, build afdb6d4

real    0m0,055s
user    0m0,030s
sys     0m0,020s
pi@pi3:~ $ time docker-compose --version
docker-compose version 1.16.1, build 6d1ac219

real    0m6,717s
user    0m6,380s
sys     0m0,260s

I installed docker-compose using pip as recommended in the official documentation. The latest Raspbian image at the time of writing is used:

pi@pi3:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 9.1 (stretch)
Release:        9.1
Codename:       stretch

same issue on mac. docker-compose version 1.5.2, build 7240ff3

I was blaming docker lately for being so slow for running phpunit, but tested it without docker-compose and was blazing fast, docker-compose is not usable for running tests, it takes more time for the container to actually run than the time needed for the tests. This needs to be fixed.

Not sure if this is the correct issue to post this but I’ve noticed considerable lag when building images. docker-compose build will sit for minutes sporadically on various steps. While I sit waiting 10 minutes for a step to complete the target machine is pretty much idling, CPU usage being well under 1% with a Gig of ram to spare. It won’t consistently lag on a particular step, it will run at “normal” speed and then decide to take a really long breather.

Server:

~$ sudo docker version
Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 4749651
OS/Arch (client): linux/amd64
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 4749651
OS/Arch (server): linux/amd64

~$ sudo docker -D info
Containers: 7
Images: 127
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 141
 Dirperm1 Supported: false
Execution Driver: native-0.2
Kernel Version: 3.13.0-40-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 2
Total Memory: 3.859 GiB
Name: webinator
ID: GWVS:RVMS:YDAI:7RIG:BA4A:GP3P:XFWL:7R4Z:ST5E:M7HG:CU2G:J2ML
Debug mode (server): false
Debug mode (client): true
Fds: 70
Goroutines: 275
System Time: Thu Apr 30 17:53:47 UTC 2015
EventsListeners: 0
Init SHA1: 9145575052383dbf64cede3bac278606472e027c
Init Path: /usr/bin/docker
Docker Root Dir: /var/lib/docker
WARNING: No swap limit support
Labels:
 provider=amazonec2

Client:

jason@jason-Lemur-Ultra:~/Repos/project-webinator/maker$ docker-compose --version
docker-compose 1.2.0
jason@jason-Lemur-Ultra:~/Repos/project-webinator/maker$ docker --version
Docker version 1.6.0, build 4749651

Same issue here with latest docker and latest docker-compose. Starting a rails console takes 12s when docker-compose up is used and about twice the time when docker-compose run is used. Really strange. How can I help to debug this?

Hint: If I add privileged: true to the docker-compose.yml, up and run are equally fast!

I solveld this question staying my Dockerfile in sub-folder.

php: restart: always
build: . ports:

• “80:80”
• “443:443” volumes:
• .:/var/www/html links: - db

db: restart: always image: mysql:5.6 ports: - “3306:3306” environment: MYSQL_ROOT_PASSWORD: 123 DB_NAME: pass DB_PASS: 123 DB_USER: pass volumes: - ./mysql/databases:/var/lib/mysql - ./logs/mysql:/var/log/mysql

to

php: restart: always
build: ./php ports:

• “80:80”
• “443:443” volumes:
• .:/var/www/html links: - db

db: restart: always image: mysql:5.6 ports: - “3306:3306” environment: MYSQL_ROOT_PASSWORD: pass DB_NAME: test DB_PASS: pass DB_USER: test volumes: - ./mysql/databases:/var/lib/mysql - ./logs/mysql:/var/log/mysql

I am also running into a 2X performance hit when comparing docker-compose up vs docker-compose run. I have a mongo, rabbit, mysql, and test containers where the test container interacts with mongo, rabbit and mysql. We run java gradle unit tests in this test container that produces a lot of log output to STDOUT. When I run using “up” the tests take about 12 minutes when using “run” it takes 24 minutes to execute. I was preferring the “run” option as I plan to execute this in jenkins but considering the performance issues I’ll have to use “up” and put the process in the background and monitor it until it’s done before finishing the jenkins job. Is there a chance when you use “run” it uses a different network resulting in slower communication as it does talk to mongo and rabbit a lot. Any ideas or suggested approaches for this?

@thaJeztah Yes, sure!. The issue is #3419

No, I’m running ubuntu.