-
Notifications
You must be signed in to change notification settings - Fork 110
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
Docker-ce 25.0.0 breaks image squashing #236
Comments
Might be related to moby/moby#44598 |
Looks like the exported image old/blobs dir has stripped the
|
We had the same issue after docker-ce and docker-ce-cli was auto-upgraded from version 24.0.7 to 25.0.0 on our build machine. As a workaround we downgraded to the 24.0.7 docker packages which resolved the issue.
|
Do we need to manually generate a tarball now? What's the suggestion for compatibility with 25.0.0? |
Same issues on our end as well with Docker |
Thanks for the report. I can confirm that due to Docker 25.x switching to the OCI archive format it is incompatible with docker-squash which currently only supports docker-archive format. Note that podman currently saves by default in docker-archive format but is also planning on switching in its next major release. It would effectively need a completely new v3_image.py implementation to handle the different format. |
I am currently looking into this and examining the differences between the different formats. Primarily instead of e.g. |
Is there any chance of getting a new tagged release so we don't have to install from git to get this fix? |
Thank you for the quick fix :) |
We should be now good to go! https://pypi.org/project/docker-squash/1.2.0/ Big ups for @rnc for stepping in to fix this! |
There is an issue with using docker-squash and the latest stable docker release. Using the example Dockefile
and building it via
I can successfully squash an image with docker-ce version 24.0.7, see
v24.0.7.log
However, if I use docker-ce 25.0.0 I get
I'm going to look further into this but thought raising an issue already might help
The text was updated successfully, but these errors were encountered: