Re: How to pull images from a remote registry with the actual layers instead of just metadata?

On Sat, Nov 18, 2017 at 3:16 PM, Joel Pearson wrote: > It would introduce a new final layer right? Because after every build, > OpenShift automatically adds a bunch of labels? yeah that's true, sorry completely blanked on that. > > On Sun, 19 Nov 2017 at 7:13

Re: How to pull images from a remote registry with the actual layers instead of just metadata?

It would introduce a new final layer right? Because after every build, OpenShift automatically adds a bunch of labels? On Sun, 19 Nov 2017 at 7:13 am, Ben Parees wrote: > On Sat, Nov 18, 2017 at 2:54 AM, Joel Pearson < > japear...@agiledigital.com.au> wrote: > >> Ahh ok. Is

Re: How to pull images from a remote registry with the actual layers instead of just metadata?

On Sat, Nov 18, 2017 at 2:54 AM, Joel Pearson wrote: > Ahh ok. Is there some way to abuse build config‘s to push existing images > to remote OpenShift registries? technically you could probably have a dockerfile that just says "FROM imagex" and nothing else, and

RE: How to pull images from a remote registry with the actual layers instead of just metadata?

Hi This limitation or ”design” of the oc import-image and also the limitations of Docker push where one needs to have the image locally to be able to push it, is the reason why we have shifted to use Skopeo for all such Docker image importing. We have two OpenShift environments with

Re: How to pull images from a remote registry with the actual layers instead of just metadata?

Wow! Thanks Lars, I’ll try out your ideas on Monday. On Sat, 18 Nov 2017 at 10:34 pm, Lars Milland wrote: > Hi > > > > This limitation or ”design” of the oc import-image and also the > limitations of Docker push where one needs to have the image locally to be > able to push it,

Re: How to pull images from a remote registry with the actual layers instead of just metadata?

Ahh ok. Is there some way to abuse build config‘s to push existing images to remote OpenShift registries? On Sat, 18 Nov 2017 at 6:15 pm, Ben Parees wrote: > On Sat, Nov 18, 2017 at 2:12 AM, Joel Pearson < > japear...@agiledigital.com.au> wrote: > >> So there is no way with

Re: How to pull images from a remote registry with the actual layers instead of just metadata?

On Sat, Nov 18, 2017 at 2:12 AM, Joel Pearson wrote: > So there is no way with the oc command to import an image and not have it > need the remote to exist after that? I’d just have to use docker push > instead? currently that is correct. > > On Sat, 18 Nov

Re: How to pull images from a remote registry with the actual layers instead of just metadata?

So there is no way with the oc command to import an image and not have it need the remote to exist after that? I’d just have to use docker push instead? On Sat, 18 Nov 2017 at 6:04 pm, Ben Parees wrote: > On Sat, Nov 18, 2017 at 1:13 AM, Lionel Orellana >

Re: How to pull images from a remote registry with the actual layers instead of just metadata?

On Sat, Nov 18, 2017 at 1:13 AM, Lionel Orellana wrote: > So it sounds like the local option means after it’s pulled once it will >> exist in the local registry? > > > Hmm It always seems to do the pull-through >

Re: How to pull images from a remote registry with the actual layers instead of just metadata?

Thanks Lionel. I guess one way to make it secure would be to have a certificate that’s valid on the internet. But I guess it’s not really important if it’s all internal traffic. I’ll try out that local option I think that’s what I want. Because I don’t want to have to rely on the remote registry

How to pull images from a remote registry with the actual layers instead of just metadata?

Hi, I'm using OpenShift 3.6.1 in AWS and I tried using "oc import-image" to pull an image from one openshift cluster to another. I setup the docker secrets, and it appeared to be working as there was a bunch of metadata visible in the image stream. However, when actually started a pod, it