-
Notifications
You must be signed in to change notification settings - Fork 84
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
fetcher: new implementation using unlinked files #1061
Conversation
55cf8b0
to
0c750f5
Compare
Codecov ReportAttention:
... and 3 files with indirect coverage changes 📢 Thoughts on this report? Let us know!. |
3af7059
to
d3bb619
Compare
Supersedes and closes #652. |
d3bb619
to
d5e8698
Compare
eb731bc
to
b925cbf
Compare
I think this is in a place to get reviewed if you can find time. What it does (roughly in order):
There's still work to be done to move everything over to using the |
b925cbf
to
adb1c28
Compare
I can also cherry-pick some the of not strictly related |
Proposed changelog entry: libindex: move to O_TMPFILE fetcher This release uses a new fetcher (the component responsible for pulling layers |
1f45682
to
cc3cdb3
Compare
This fetcher implementation uses the O_TMPFILE flag to open(2) to open files that are not linked into the file system. Doing this means that the layer contents are cleaned up even if the process exits uncleanly. Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
…ription` There's too many of these things. Signed-off-by: Hank Donnay <hdonnay@redhat.com>
These tests should probably be audited and removed where they don't make sense anymore. Signed-off-by: Hank Donnay <hdonnay@redhat.com>
This makes gomock a bit nicer to use. Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
efa103a
to
58b6b4a
Compare
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.
Concerns addressed face to face, LGTM
Since quay/claircore#1061 we should no longer need the pre-removal of fetch layers. Signed-off-by: crozzy <joseph.crosland@gmail.com>
Since quay/claircore#1061 we should no longer need the pre-removal of fetch layers. Signed-off-by: crozzy <joseph.crosland@gmail.com>
I've tried to do this like 3 times and think I finally hit on a way to only gradually break the API.
Todo: