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 image pull after a failure #1916
Conversation
When resuming from a failed pull writer.Truncate() was not seeking to the proper position in the file. This caused writes to happen after the previously written content, instead of at the start of the file. Signed-off-by: Daniel Nephin <dnephin@gmail.com>
appveyor timed out, doesn't seem related to the changes in this PR |
Wow, some of the tests are taking a minute to ran, hence the timeout. Might be due to a recent change |
Restart the build, hopefully it was just an issue on appveyor side |
Codecov Report
@@ Coverage Diff @@
## master #1916 +/- ##
==========================================
+ Coverage 47.29% 47.32% +0.02%
==========================================
Files 89 89
Lines 8830 8833 +3
==========================================
+ Hits 4176 4180 +4
+ Misses 3968 3965 -3
- Partials 686 688 +2
Continue to review full report at Codecov.
|
Should we cherry pick this? This seems not good to me. |
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #1893
When resuming from a failed pull the local content store
Writer.Truncate()
was not seeking to the proper position in the file. This caused writes to happen after the previously written content, instead of at the start of the file. Ref https://golang.org/pkg/os/#File.Truncate ( It does not change the I/O offset)Truncate()
is called from https://github.com/containerd/containerd/blob/v1.0.0/services/content/service.go#L395-L399.