summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/GitPython/hardcode-git-path.patch
diff options
context:
space:
mode:
authorBrian McKenna <bmckenna@atlassian.com>2016-03-10 18:29:28 +1100
committerBrian McKenna <bmckenna@atlassian.com>2016-04-11 16:32:43 +1000
commitebb911cc0b31dd39dfaf61f206967e47e92547cb (patch)
tree7501d675addb18bc27cef348af6b69ef56fd088c /pkgs/development/python-modules/GitPython/hardcode-git-path.patch
parent3ef785eaa6676b2fe2de9dd46eb734f07a7abc99 (diff)
dockerTools: remove tarballs functionality
I think the intention of this functionality was to provide a simple alternative to the "runAsRoot" and "contents" attributes. The implementation caused very slow builds of Docker images. Almost all of the build time was spent in IO for tar, due to tarballs being created, immediately extracted, then recreated. I had 30 minute builds on some of my images which are now down to less than 2 minutes. A couple of other users on #nix IRC have observed similar improvements. The implementation also mutated the produced Docker layers without changing their hashes. Using non-empty tarballs would produce images which got cached incorrectly in Docker. I have a commit which just fixes the performance problem but I opted to completely remove the tarball feature after I found out that it didn't correctly implement the Docker Image Specification due to the broken hashing.
Diffstat (limited to 'pkgs/development/python-modules/GitPython/hardcode-git-path.patch')
0 files changed, 0 insertions, 0 deletions