Skip to content

Conversation

@mtrmac
Copy link
Collaborator

@mtrmac mtrmac commented Jun 27, 2016

This is a placeholder for the discussion in containers/skopeo#97 ; real implementation will be different, I just didn’t want to close that one with nothing to point to.

Without this, processing dir: sources would fail on the
reference.ParseNamed immediately below, even with insecureAcceptAnything
policy.

FIXME: Is this the right thing to do? Allowing local dir: like this
might tempt users to use default:insecureAcceptAnything, which would not
do.

Alternatives:
- Hard-code allowing for unidentified images?
- Add a new local:, or unidentified: stanza?
- Replace default/specific[dockerReference] with an
  imageType:[somenamespace] (as a single string or object hierarchy?),
  which would natively support dir: (and allow different semantics for
  dir:/file/system/path and docker://full-format/reference/with:hostname )

The last one seems best ATM.

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
@mtrmac mtrmac force-pushed the unidentified-images branch from 99ebc75 to b88d71c Compare July 12, 2016 13:40
@mtrmac
Copy link
Collaborator Author

mtrmac commented Jul 18, 2016

Replaced by #33 .

@mtrmac mtrmac closed this Jul 18, 2016
@mtrmac mtrmac deleted the unidentified-images branch July 18, 2016 13:29
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.

1 participant