umoci: update to get tar writing fix #597
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
move umoci version to the commit with the fix for correctly closing tarwriter in all cases, avoiding creation of layers that make gnu tar sad.
What type of PR is this?
bug
Which issue does this PR fix:
What does this PR do / Why do we need it:
while golang based container tools ignore this EOF, which is fine because it only happens after the last file has been read, many scanners use gnu tar, which errors out and can cause problems.
If an issue # is not available please add repro steps and logs showing the issue:
see project-stacker/umoci#4
Testing done on this change:
see project-stacker/umoci#4
Will this break upgrades or downgrades?
no
Does this PR introduce any user-facing change?:
no
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.