containers
BUG: run: extracttar error: exit status 1, output: error extracting tar
- in a test, we have 3 linearly dependent images:
image/test-1
acbuild ...
image/test-2
acbuild dep add image/test-1
acbuild ...
image/test-3
acbuild dep add image/test-2
acbuild ...
-
when each image is small, build for all of them works fine
-
when each image size gets to some 100 MB (individually, compressed), the following error starts to occur during image/test-3 build, after image/test-2 download:
run: extracttar error: exit status 1, output: error extracting tar
-
the only apparent breaking point trigger is adding more packages to the image, not clear why: https://github.com/appc/acbuild/blob/master/vendor/github.com/coreos/rkt/pkg/tar/chroot.go#L89
-
the following workaround makes the build work again:
image/test-3
acbuild dep add image/test-1
acbuild dep add image/test-2
acbuild ...
-
but that does not scale due to lack of cache https://github.com/appc/acbuild/issues/125
-
using release https://github.com/appc/acbuild/releases/tag/v0.3.1
Sorry about the slow responses, currently in the middle of some other work.
Unless you're able to make an acbuild script that can reproduce this, that tar error is nowhere near descriptive enough for me to start hunting around as to what is causing this. I threw together a little patch to get acbuild to always print the full details for tar errors, would you be willing to run this patch on your system and share the output?
-
thank you for the PR
-
patch did not help, still same error
run: extracttar error: exit status 1, output: error extracting tar -
I will try to produce build script decoupled from internal dependencies
-
please bake version/branch/tag into acbuild - its easy to get lost in patches
The patch didn't work? That's really interesting...
As far as baking version/branch/tag into acbuild, at the very least acbuild version should report the most recent tag + a commit hash (assuming you're building with the build tag). Would adding branch information also be useful there?
@sanicheev would you be able to share more information about your setup? If I can reproduce this, I might be able to fix it.
Things that might be useful:
- distribution
- filesystem
- are you using a release from github, or did you build it yourself?
- if you built it yourself, golang version?
- would you be willing to share your build script?
hello - Is there an issue with size of files that go into build "acbuild dep add filename.tar" . I have a big file filename.tar/10GB that goes as part of that. I noticed acbuild completes successfully but during the time of rkt run image I get following error: rkt --debug --insecure-options=image run --interactive sas94m5-linux-amd64.aci image: using image from local store for image name coreos.com/rkt/stage1-coreos:1.29.0 image: using image from file /usr/lib/rkt/stage1-images/stage1-coreos.aci image: using image from file /opt/rkt_images/sas94m5-linux-amd64.aci run: └─error rendering tree store └─cannot render aci └─error extracting ACI └─extracttar error: exit status 254, output: error extracting tar:
Sudhir Nallagangu
