Skip to content

copy: add shared blob directory support for OCI sources/destinations - #443

Merged
mtrmac merged 2 commits into
podman-container-tools:masterfrom
nstack:shared-blobs
Nov 6, 2017
Merged

copy: add shared blob directory support for OCI sources/destinations#443
mtrmac merged 2 commits into
podman-container-tools:masterfrom
nstack:shared-blobs

Conversation

@jonboulle

Copy link
Copy Markdown
Contributor

Following on from containers/image#369, this adds command-line flags to skopeo copy which allow users to use a shared directory for blobs when working with OCI layouts.

@runcom this patch is nice and tiny, but is there a better way to scope flags to specific source/dest types?

@mtrmac

mtrmac commented Nov 6, 2017

Copy link
Copy Markdown
Contributor

👍 pending tests.

Currently there isn’t a better way. In principle parseImage* + contextFrom* could work together to ensure that the user does not specify context options which would be ignored by the user-specified image reference.

@runcom

runcom commented Nov 6, 2017

Copy link
Copy Markdown
Contributor

Well, we could enhance the OCI référence format to take options in the reference string itself but best to go with this now.

@runcom

runcom commented Nov 6, 2017

Copy link
Copy Markdown
Contributor

LGTM

@runcom

runcom commented Nov 6, 2017

Copy link
Copy Markdown
Contributor

looks like this needs a rebase already? wtf

Only works for OCI layout sources and destinations.
@jonboulle

Copy link
Copy Markdown
Contributor Author

That's.... odd

From github.com:projectatomic/skopeo
   62c6899..0d0055d  master     -> origin/master
Updating 62c6899..0d0055d
Fast-forward
 CONTRIBUTING.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Anyway, updated now

@mtrmac

mtrmac commented Nov 6, 2017

Copy link
Copy Markdown
Contributor

Well, we could enhance the OCI référence format to take options in the reference string itself

That introduces undesirable string parsing and joining, and issues like ”are two images the same if they only differ in an option?”.

The contextFromGlobalOptions could just notice that it is setting options for a transport which does not match the transport of a reference. (Which would be even easier if SystemContext did not embed all options directly, but only carried a pointer to an optional separate structure for each transport/topic. We might eventually need to do that just to prevent SystemContext from being too big.)

Anyway, that’s for someone’s Copious Spare Time.

@mtrmac
mtrmac merged commit 24423ce into podman-container-tools:master Nov 6, 2017
@jonboulle
jonboulle deleted the shared-blobs branch November 6, 2017 18:10
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Oct 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants