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

[RFC Do not merge] Add copy.Options.LayerSubset. #159

Closed
wants to merge 1 commit into from

Conversation

mtrmac
Copy link
Collaborator

@mtrmac mtrmac commented Nov 8, 2016

For now just to get an idea of what this would take…

FIXME: Should come with more warnings.

This is needed to allow the Python code in atomic to only download the subset of layers which is not already available locally, while still verifying signatures and validating layer digests (per discussion in
containers/skopeo#242 ).

@runcom
Copy link
Member

runcom commented Nov 8, 2016

makes sense

@mtrmac
Copy link
Collaborator Author

mtrmac commented Nov 10, 2016

@runcom @guiseppe I will not be finishing this this week; feel free to take this over if you like the approach and there is time pressure, or we can turn this into a Trello card to be finished later.

@runcom
Copy link
Member

runcom commented Nov 10, 2016

I don't think we're in any hurry here. We're not going to drop skopeo layers any soon (at least till we have something like this).

@mtrmac mtrmac force-pushed the copy-layers-list branch 4 times, most recently from cfd4ced to 18a5bb0 Compare November 29, 2016 20:27
@mtrmac mtrmac force-pushed the copy-layers-list branch 4 times, most recently from 72c8357 to 9a9b5c0 Compare December 8, 2016 23:04
@mtrmac mtrmac force-pushed the copy-layers-list branch 3 times, most recently from 67562aa to cd286a2 Compare January 9, 2017 16:49
giuseppe pushed a commit to giuseppe/image that referenced this pull request Jan 24, 2017
minor cleanup for build issues related to the manual
@mtrmac mtrmac force-pushed the copy-layers-list branch 5 times, most recently from 474edbb to f13f317 Compare February 6, 2017 16:08
@mtrmac mtrmac force-pushed the copy-layers-list branch 3 times, most recently from e0217d4 to d417b74 Compare March 2, 2017 20:08
@mtrmac
Copy link
Collaborator Author

mtrmac commented Apr 21, 2017

This should no longer be necessary with #228. Can I close this PR, or am I missing anything?

FIXME: Should come with more warnings.

This is needed to allow the Python code in atomic to only download the
subset of layers which is not already available locally, while still
verifying signatures and validating layer digests (per discussion in
containers/skopeo#242 ).

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
@mtrmac
Copy link
Collaborator Author

mtrmac commented Apr 26, 2017

Assuming this is superseded by #228 , closing.

@mtrmac mtrmac closed this Apr 26, 2017
@mtrmac mtrmac deleted the copy-layers-list branch April 26, 2017 14:51
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.

2 participants