Sending build context to Docker daemon is slow

[BastianHofmann]

When I run a docker build the Sending build context to Docker daemon step is slow. It always loads a few MB then it stops for a few seconds before it starts loading the next few MBs.

OSX 10.10.3
Vagrant 1.7.2
VirtualBox 4.3.20
Docker version 1.5.0, build a8a31ef

[codekitchen]

Is this specific to one project, or are you seeing this behavior across all docker builds? I'm not aware of anybody else who has run into this. I had one other report of something similar a while back, but it turned out the project just had huge .git and node_modules dirs that weren't in .dockerignore.

[BastianHofmann]

In this case I'm sendibg abou 250mb. It worked fine with boot2docker.

Sent from my iPhone

On 13.05.2015, at 17:23, Brian Palmer [email protected] wrote:

Is this specific to one project, or are you seeing this behavior across all docker builds? I'm not aware of anybody else who has run into this. I had one other report of something similar a while back, but it turned out the project just had huge .git and node_modules dirs that weren't in .dockerignore.

—
Reply to this email directly or view it on GitHub.

[lmakarov]

Had the same issue, see lmakarov/boot2docker-vagrant#13 for a solution.

[codekitchen]

Oh that's a great tip, thanks @lmakarov

I'll get this into the next release, in the meantime @BastianHofmann you could manually add this fix to /usr/local/var/dinghy/vagrant/Vagrantfile. I'd love to hear if that solves it for you.

[BastianHofmann]

Will do.

On 13 May 2015, at 18:43, Brian Palmer [email protected] wrote:

Oh that's a great tip, thanks @lmakarov https://github.com/lmakarov
I'll get this into the next release, in the meantime @BastianHofmann https://github.com/BastianHofmann you could manually add this fix to /usr/local/var/dinghy/vagrant/Vagrantfile. I'd love to hear if that solves it for you.

—
Reply to this email directly or view it on GitHub #19 (comment).

[BastianHofmann]

Works great!

On 13 May 2015, at 18:43, Bastian Hofmann [email protected] wrote:

Will do.

On 13 May 2015, at 18:43, Brian Palmer <[email protected] mailto:[email protected]> wrote:

Oh that's a great tip, thanks @lmakarov https://github.com/lmakarov
I'll get this into the next release, in the meantime @BastianHofmann https://github.com/BastianHofmann you could manually add this fix to /usr/local/var/dinghy/vagrant/Vagrantfile. I'd love to hear if that solves it for you.

—
Reply to this email directly or view it on GitHub #19 (comment).

[codekitchen]

Hooray! VM networking is still mostly a mystery to me, I'm afraid. I'll get this fix in.

[eibrahim]

I fixed it by moving my Dockerfile and docker-compose.yml into a subfolder called docker and it worked. Apparently docker sends the current folder to the daemon and my folder was 9 gigs.

[lmakarov]

@eibrahim If you don't want Docker to pick up your entire folder during the build, you can use a .dockerignore file - https://docs.docker.com/reference/builder/#dockerignore-file

E.g., .dockerignore:

*

[eibrahim]

Great tip. Didn't think of adding * to .dockerignore. Thanks.

[kvz]

Adding to this, you can use e.g.:

*
!stack.statuspage

to create a whitelist, vs a blacklist.