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

fix(umoci)!: umoci's copy buffer set to 1 MiB (#531) #536

Closed
wants to merge 3 commits into from

Conversation

rchincha
Copy link
Contributor

@rchincha rchincha commented Nov 8, 2023

  • fix(umoci)!: umoci's copy buffer set to 1 MiB

project-stacker/umoci@89a7ea1

Use updated umoci (project-stacker's fork) to use a 1 MiB copy buffer. This change brings stacker inline with compression parameters used in containers/image libraries and makes them compatible.

  • test(gzip): add unit tests for gzip

(cherry picked from commit 589a648)

What type of PR is this?

Which issue does this PR fix:

What does this PR do / Why do we need it:

If an issue # is not available please add repro steps and logs showing the issue:

Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?

Does this PR introduce any user-facing change?:


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

* fix(umoci)!: umoci's copy buffer set to 1 MiB

project-stacker/umoci@89a7ea1

Use updated umoci (project-stacker's fork) to use a 1 MiB copy buffer.
This change brings stacker inline with compression parameters used in
containers/image libraries and makes them compatible.

Signed-off-by: Ramkumar Chinchani <[email protected]>

* test(gzip): add unit tests for gzip

Signed-off-by: Ramkumar Chinchani <[email protected]>

---------

Signed-off-by: Ramkumar Chinchani <[email protected]>
(cherry picked from commit 589a648)
Signed-off-by: Ramkumar Chinchani <[email protected]>
@smoser
Copy link
Contributor

smoser commented Nov 8, 2023

I had just done #537 (and then saw that you did this).

I'm surprised that your branch could work. the test you added I do not think can pass because it tests that it is using SKOPEO at a certain version, and you're not going to build that version.

i think mine should get skopeo built.

@hallyn
Copy link
Contributor

hallyn commented Nov 8, 2023

I'm surprised that your branch could work

Hm, he didn't add SKPOEO to the make targets so maybe it didn't actually build it?

Signed-off-by: Ramkumar Chinchani <[email protected]>
@hallyn
Copy link
Contributor

hallyn commented Nov 8, 2023

Do you need to add the build-deps as in Scott's pr?

Signed-off-by: Ramkumar Chinchani <[email protected]>
@rchincha rchincha closed this Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants