-
Notifications
You must be signed in to change notification settings - Fork 783
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
Expose copy.Options.ForceCompressionFormat #2343
Comments
Thanks for your report. This is tracked in containers/image#1270 ; fixing that could break uploads to some registries. As described there, the code now allows forcing compression to happen, ~avoiding the MIME type inconsistency. That option does not currently exist in Skopeo, it could be added. |
skopeo copy
with uncompressed layers input creates manifest incorrectly reporting layers are compressed.docker-archive
creates manifest incorrectly reporting layers are compressed.
Got it. My workaround now is to first push to a |
To be clear, this was not
|
Would you care to file a Skopeo PR to expose containers/image#2068 ? That might be the simplest way to do this in one step. (“ |
Thanks for the context! |
docker-archive
creates manifest incorrectly reporting layers are compressed.
A friendly reminder that this issue had no activity for 30 days. |
Steps to reproduce:
test.tar
) that uses uncompressed tarballs as layersskopeo copy docker-archive:test.tar dir://out
out/manifest.json
has layers specified as"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip"
e719c9bac8ba3f1aac6ab6d3dbd006be2bee3dca4030e0fca96297ba72bdb569/layer.tar: POSIX tar archive
The text was updated successfully, but these errors were encountered: