Bug 7016

Summary:	Git issues in resulting buildroot tar
Product:	buildroot	Reporter:	Brian Clements <brian>
Component:	Other	Assignee:	unassigned
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	buildroot
Priority:	P5
Version:	2014.02
Target Milestone:	2014.05
Hardware:	PC
OS:	Linux
Host:		Target:
Build:

Description Brian Clements 2014-04-01 19:41:38 UTC

Hi There,
Sorry if this isn't the correct place for this bug, please forward me if so.

I've built a pretty standard busybox chain using many different options and versions of git by this point, but the end result has been the same: using git in this freshly built image fails on anything involved decompressing objects (git clone among other things).

The context here has been to make a Docker image of busybox with a complete git install contained therein. All my reproducible steps are here:

https://github.com/brianclements/dockerfile-busyboxplus/blob/gitbug/tarmaker/Dockerfile

I've even tried substituting different versions of buildroot (2013.08.1, 2014.02) and different versions of git (1.8.3, 1.8.5.3, 1.9.0) all with the same result. The build succeeds, and the resulting image works as far as I can tell, but running "git clone" on a larger repository that involves compression of objects (smaller repos of text only work fine) will fail with: 

fatal: serious inflate inconsistency   
fatal: index-pack failed

Any thoughts or further testing I can try to tweak the git build?

Thanks.

Comment 1 Thomas De Schampheleire 2014-04-02 07:35:03 UTC

Can you provide more details on how you actually run this image? I am not familiar with Docker, so more details about how you run this is very welcome.

Have you tried using a similar configuration on a non-docker environment, like qemu or a real target?

Also, did you try to run git through 'strace' to see what is actually going on?
Have you tried making a new local git repo using the git inside this image, and then clone that with the same git? Or have you only tried cloning an external git repo? If there is a problem with importing git data, the inflate can obviously fail. Generating a local git repo would help excluding that.

For reference to others, here seems to be the basic flow to generate docker image using buildroot: (Jerome Petazzoni)
http://blog.docker.io/2013/06/create-light-weight-docker-containers-buildroot/

Comment 2 Thomas De Schampheleire 2014-05-14 08:13:47 UTC

Investigation was discussed further on the mailing list, see
http://lists.busybox.net/pipermail/buildroot/2014-April/093307.html
http://lists.busybox.net/pipermail/buildroot/2014-May/095513.html

The issue could not be reproduced using the same configuration in qemu.
My assumption is that the way the rootfs is run through docker is causing trouble, and thus that it isn't a buildroot problem.
Therefore, I'm going to close this bug.

Brian: do not hesitate to continue the discussion on the mailing list, or to reopen this bug if you think it effectively is a buildroot bug.

Thanks.