Skip to content
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

skopeo copy fails copying from a tarball to Docker daemon when using Docker 26.1.3 #2365

Open
phlax opened this issue Jun 23, 2024 · 3 comments

Comments

@phlax
Copy link

phlax commented Jun 23, 2024

Our (Envoy proxy) CI uploads some images from a tarball created by other CI

This worked as expected with Docker version 24.0.9.

Recently Github updated its runner images. The newer images use Docker 26.1.3

Since this change our CI reliably fails with:

Copy oci image: oci-archive:/tmp/tmp.TebmJdN0Xs/envoy.tar docker-daemon:envoyproxy/envoy:dev
time="2024-06-22T22:47:03Z" level=fatal msg="writing blob: io: read/write on closed pipe"

I have tried to repro the issue locally using the same Docker version/s but it works as expected.

I suspect this is a similar issue to #1627 where a source resource is producing data too slowly for the daemon

Not sure if this is a skopeo issue as such, but we are hitting it while trying to load using skopeo so reporting here

Any workarounds would be greatly appreciated, I would also be happy to debug further if this is helpful

@phlax phlax changed the title skopeo copy fails copying from a tarball to Docker registry when using Docker 26.1.3 skopeo copy fails copying from a tarball to Docker daemon when using Docker 26.1.3 Jun 23, 2024
@mtrmac
Copy link
Collaborator

mtrmac commented Jun 24, 2024

Thanks for reaching out.

What version of Skopeo are you using? The version difference crosses containers/image#2259 , fixed in recent versions.

Alternatively, using skopeo --debug copy should reveal a bit more. In particular a message containing docker-daemon: sending done, status… might be relevant, but there may be others.

@phlax
Copy link
Author

phlax commented Jul 3, 2024

apologies for slow response - we are currently downgrading docker to work around the issue.

i will set up some CI to try and capture the debug log as suggested, altho it may take me a little while - thanks.

Copy link

github-actions bot commented Aug 3, 2024

A friendly reminder that this issue had no activity for 30 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants