-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using ADD with XZ compressed tarball fails #55
Comments
Hmm, thanks for the report but I don't really know what I can do about it. 🤔 This is a pretty thin wrapper around Buildkit and I have no idea why From a quick browse through the codebase, it looks like it just doesn't support it: I'll leave this open since it sounds like you tested with Buildkit directly, and maybe others will run into it too, but I don't anticipate changing anything on my end. :/ |
I'm not sure where this is coming from then. I'm gonna test out with buildkit on a clean debian10 vm without docker or any of its dependencies installed. |
Okay, so i've ran this with I also tried grabbing the runc that's packaged in my concourse and putting it into the vm so that buildkitd can use that as well, same result, build succeeds. |
Apologies for a potentially slim bug report, but it would appear that oci-build-task only supports uncompressed tarballs.
This has caused a few days of banging my head against the wall trying to figure out why it fails.
I was building an image from scratch:
The error output from running a task configured as such:
was a variant of this:
Unpacking the xz-compressed rootfs was enough to get this to build correctly.
This dockerfile worked just fine with normal
docker build
andbuildctl build
.The text was updated successfully, but these errors were encountered: