Compose: docker compose build is slow with existing volumes
Hello!
I have a nextcloud installation, and I notice that once the size of your volumes gets big (20GB) updating the container images using
docker-compose build --pull
becomes very slow (tens of minutes) on linux. Is that normal behaviour?
My volumes are mapped to host directories.
I can fix the issue by temporarily moving the volumes folders before running the command, but ideally, I wouldn't have to do that.
Cheers!
ghost
All 3 comments
Your mounts are probably part of your build context (typically your application folder). When you trigger a build, Compose makes a tar archive of your build context and sends it to the engine. That can take a while if you have a lot of data to archive.
The solution is to either mount these folders outside of your build context, or add them to your .dockerignore.
HTH!
shin-
on 27 Feb 2018
Yes, that was the issue, I moved out the volumes and now it works great!
Thanks for your help.
ghost
on 28 Feb 2018
hello , can you help me how to move out the volumes , i mean the way that you done please ?
hakimFUT
on 23 Aug 2018
Related issues
giggio
路
3Comments
bitver
路
3Comments
komuw
路
3Comments
dimsav
路
3Comments
29e7e280-0d1c-4bba-98fe-f7cd3ca7500a
路
3Comments
Most helpful comment
Your mounts are probably part of your build context (typically your application folder). When you trigger a build, Compose makes a tar archive of your build context and sends it to the engine. That can take a while if you have a lot of data to archive.
The solution is to either mount these folders outside of your build context, or add them to your
.dockerignore.HTH!