Comments (5)
How would that work?
If we start with the OpenShift API URL, we have a plausible way to discover the docker registry API URL (it doesn’t work, but hopefully it will one day).
Given the docker registry API URL, how would we find the corresponding OpenShift API URL?
from skopeo.
Independently of the primary concern above, WRT the --atomic
CLI option:
“Transports” (the designated by the prefix before a colonwhen referring to an image for skopeo
) are a fairly fundamental abstraction in containers/image and skopeo copy
. The docker:
/ atomic:
prefix is there precisely so that any application, whether skopeo, ocid, or anything else, can use any image recognized by containers/image without understanding the specifics of it. If skopeo had a special --atomic
option then every other user of containers/image would have to have its own equivalent to the --atomic
option; generic software which didn’t support this option wouldn’t allow using the OpenShift API.
(Of course the user can just forget about OpenShift and manually discover the location of the embedded docker registry, and use that using the plain docker://
image names, but that means docker registry-like behavior and no OpenShift API use.)
(Also, of course it is possible to build a CLI on top of containers/image which does not expose these transport designation prefixes—and atomic
is one such a CLI already. skopeo
is, as much as practical, just a thin dumb wrapper over containers/image.)
Finally, if #189 is high-priority, please just say so; it is ugly but doable, I’m just not working on it right now because I am guessing (perhaps incorrectly) that it is not a critical deliverable.
from skopeo.
Given the docker registry API URL, how would we find the corresponding OpenShift API URL?
The same way we define the lookaside cache using the atomic.conf configuration file.
My primary concern is that users expect to reference by fully qualified docker registry name. They're not aware of signing servers, they just have an image. Some are not even aware of imagestreams and project namespace.
“Transports” (the designated by the prefix before a colonwhen referring to an image for skopeo) are a fairly fundamental abstraction in containers/image and skopeo copy.
Yes, and I don't intend to put deliverables at risk for this. My specific proposal is probably a bad one.
from skopeo.
The same way we define the lookaside cache using the atomic.conf configuration file.
It’s fairly unattractive to commit to an UI which requires the user to input two bits of data when one uniquely identifies the other (in principle, though not in current implementation)
from skopeo.
Both this and #189 could be resolved by adding a registry URI to the atomic: type.
atomic:registry_uri:port/namespace/stream:tag
In this way the end user references a docker image as they expect to, regardless of their awareness of the openshift cluster. We get the registry URI and port "for free", resolving #189.
from skopeo.
Related Issues (20)
- Error parsing manifest for image HOT 2
- Using skopeo copy from Nix source to docker-daemon target produces no image HOT 2
- Skopeo Copy notation specific signatures HOT 2
- `skopeo copy docker-archive:` does not recognize media type. HOT 1
- Replaced quay.io/skopeo/stable images keep being deleted HOT 8
- Regarding skopeo libraries to be used in golang HOT 3
- inspect: Go template not working well on some images HOT 4
- Copying saved docker-tar to Registry with Same Sha value as Source Registry HOT 5
- Skopeo's ability to retain SHA value when copied from one registry to other HOT 6
- [bug]: go install github.com/containers/skopeo/cmd/[email protected] fails HOT 7
- Skopeo sync does not sync Notation signatures HOT 3
- Please release #2189 HOT 4
- Provide skopeo as a Go package HOT 2
- How to use skopeo container with credential helpers? HOT 3
- Error verifying signature: Invalid GPG signature: (*packet.Signature)( "nil)" HOT 7
- Have issue with upgrading skopeo version to 1.8.1 in ubuntu 22.04 HOT 4
- Does skopeo supports loading local docker tar.gz file into remote registry? HOT 8
- Why does updating skopeo to the latest version remove docker packages? HOT 15
- Skopeo copy job creates .kube/config directory structure failing Azure AKS kubelogin convert-kubeconfig command HOT 3
- Skopeo 1.15.0 - invalid JSON output on Mac Silicon, due to error printed HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from skopeo.