-
Notifications
You must be signed in to change notification settings - Fork 286
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
archive/tar: write too long
error when using Docker Desktop containerd backend
#2174
Comments
I was able to reproduce this with pack 0.34.0. On pack 0.33.2, I saw a different error:
|
This error appears to be coming from imgutil. I will look into it... |
…ntainerd backend Fixes buildpacks/pack#2174 This is somewhat of a band-aid solution and degrades performance because we have to read the uncompressed layer bits to get the uncompressed layer size for layers that we `docker save` out of the daemon (re-used layers and all the base layers). The better longer-term fix will be to send OCI-layout formatted tars when we have all the layers available (when using containerd as the backing store, this will always be true). Signed-off-by: Natalie Arellano <narellano@vmware.com>
buildpacks/imgutil#275 fixes Edit: linking to Slack thread, the second error looks like a bug in the daemon relating to switching back and forth between containerd storage and overlay2. |
Summary
When Docker Desktop for macOS's
containerd
feature is enabled,pack build
fails with an internalarchive/tar: write too long
error.The
containerd
backend is essential when working on multi-architecture image workflows/development, so it's quite inconvenient to have to keep turning it off when usingpack build
and then back on again when working on other repos/projects.Reproduction
Steps
git clone https://github.com/heroku/heroku-buildpack-python && cd heroku-buildpack-python
pack build --builder heroku/builder:24 --trust-builder --verbose testapp
Current behavior
Expected behavior
The
pack build
succeeds, like it does when thecontainerd
backend is not enabled.Environment
pack info
(side note: the redacted on the trusted builders list makes that information pretty useless - perhaps it should just filter any creds in repo URLs or custom (non-docker-io) repos etc?)
docker info
The text was updated successfully, but these errors were encountered: