-
Notifications
You must be signed in to change notification settings - Fork 555
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
feature request - zstd/compression support in crane copy #1501
Comments
I don't think we would add this as part of |
Part of mutate sounds good. |
Another place where it will be useful is |
This issue is stale because it has been open for 90 days with no |
not fixed yet |
This issue is stale because it has been open for 90 days with no |
not fixed yet, and I don't know how to add |
It is now possible to `crane append -f bla.tar.zstd` to upload Zstd layer, both from file and from pipe. Before this commit, crane would erroneously upload such layer with gzip mime type. While this PR does not _fully_ solve google#1501, it is very close to that. Signed-off-by: Marat Radchenko <marat@slonopotamus.org>
It is now possible to `crane append -f bla.tar.zstd` to upload Zstd layer, both from file and from pipe. Before this commit, crane would erroneously upload such layer with gzip mime type. While this PR does not _fully_ solve google#1501, it is very close to that. Signed-off-by: Marat Radchenko <marat@slonopotamus.org>
It is now possible to `crane append -f bla.tar.zstd` to upload Zstd layer, both from file and from pipe. Before this commit, crane would erroneously upload such layer with gzip mime type. While this PR does not _fully_ solve google#1501, it is very close to that. Signed-off-by: Marat Radchenko <marat@slonopotamus.org>
It is now possible to `crane append -f bla.tar.zstd` to upload Zstd layer, both from file and from pipe. Before this commit, crane would erroneously upload such layer with gzip mime type. While this PR does not _fully_ solve google#1501, it is very close to that. Signed-off-by: Marat Radchenko <marat@slonopotamus.org>
It is now possible to `crane append -f bla.tar.zstd` to upload Zstd layer, both from file and from pipe. Before this commit, crane would erroneously upload such layer with gzip mime type. While this PR does not _fully_ solve google#1501, it is very close to that. Signed-off-by: Marat Radchenko <marat@slonopotamus.org>
It is now possible to `crane append -f bla.tar.zstd` to upload Zstd layer, both from file and from pipe. Before this commit, crane would erroneously upload such layer with gzip mime type. While this PR does not _fully_ solve google#1501, it is very close to that. Signed-off-by: Marat Radchenko <marat@slonopotamus.org>
This issue is stale because it has been open for 90 days with no |
Not stale, there are two PRs that try to address this issue. |
It is now possible to `crane append -f bla.tar.zstd` to upload Zstd layer, both from file and from pipe. Before this commit, crane would erroneously upload such layer with gzip mime type. While this PR does not _fully_ solve google#1501, it is very close to that. Signed-off-by: Marat Radchenko <marat@slonopotamus.org>
It is now possible to `crane append -f bla.tar.zstd` to upload Zstd layer, both from file and from pipe. Before this commit, crane would erroneously upload such layer with gzip mime type. While this PR does not _fully_ solve google#1501, it is very close to that. Signed-off-by: Marat Radchenko <marat@slonopotamus.org>
This issue is stale because it has been open for 90 days with no |
Weird bot. |
I'd like to be able to crane copy to be able to switch compressions (zstd <-> gzip) when copying. there's a lot of tools that only support one or the other, and using crane as a utility to enable that is really helpful. we already use it as a utility for slicing multi-arch images when other runtimes/tools don't support multi-arch.
The text was updated successfully, but these errors were encountered: