Re: configuring periodic import of images

So I got it working, and I'm trying to figure out why what I did worked. I took a closer look at the packet captures where I saw what I thought was the polling. It wasn't actually good traffic, but rather the master thinking that it had a connection open to the registry server. Checking netstat

Re: configuring periodic import of images

Ok, I ran a packet capture on both the master and the docker registry and I see periodic traffic from the master to the docker container on port 5000. It's about every 30 seconds or so, so I'm assuming that it's the periodic polling. It doesn't appear that it's picking up a difference between the

Re: configuring periodic import of images

Yes, scheduled=true will poll the upstream registry. On Tue, Aug 16, 2016 at 1:59 PM, Tony Saxon wrote: > Ok, that makes sense. But I am understanding correctly that when you use > scheduled=true that it should periodically poll the source registry and > pull the latest

Re: configuring periodic import of images

Ok, that makes sense. But I am understanding correctly that when you use scheduled=true that it should periodically poll the source registry and pull the latest tag configured if it's newer than what is currently pulled? On Tue, Aug 16, 2016 at 1:48 PM, Clayton Coleman

Re: configuring periodic import of images

Can someone tell me if I'm understanding the difference between alias=true and scheduled=true for tagging imagestreams as documented at https://docs.openshift.org/latest/dev_guide/managing_images.html#adding-tag ? The way I read it is that alias true will track the source image tag and update the

Re: configuring periodic import of images

I'm using a registry deployed from a docker compose: registry: restart: always image: registry:2.2.1 ports: - 5000:5000 environment: REGISTRY_HTTP_TLS_CERTIFICATE: /certs/domain.crt REGISTRY_HTTP_TLS_KEY: /certs/domain.key REGISTRY_AUTH: htpasswd

Re: configuring periodic import of images

Did a test, but the import looks like it works correctly for hub images. In this case are you using a regular Docker registry, the integrated registry, or a third party Docker registry? On Mon, Aug 15, 2016 at 3:34 PM, Clayton Coleman wrote: > It's currently 15 minutes: > >

Re: configuring periodic import of images

It's currently 15 minutes: imagePolicyConfig: disableScheduledImport: false maxImagesBulkImportedPerRepository: 5 maxScheduledImageImportsPerMinute: 60 scheduledImageImportMinimumIntervalSeconds: 900 Will take a look and see if I can recreate this issue. On Mon, Aug 15, 2016 at 2:33

Re: configuring periodic import of images

So I've found that if I tag the imagestream manually, that it is able to pull down the latest changes and deploys them to my app: oc tag --source=docker --scheduled=true docker-lab.example.com:5000/testwebapp:latest testwebapp:latest [root@os-master ~]# oc describe is Name:

Re: configuring periodic import of images

There are logs showing that it's detecting that the imagestream has changed, but doesn't seem like there's any explanation of why it can't get it: Aug 15 08:18:10 os-master origin-master: I0815 08:18:10.446822 77042 image_change_controller.go:47] Build image change controller detected

Re: configuring periodic import of images

Right, I get the v1schema vs v2schema issue. What I'm saying is that I've already been able to import the image from the private docker repository into an imagestream: [root@os-master ~]# oc describe is Name: testwebapp Created:24 hours ago Labels:

Re: configuring periodic import of images

To have openshift import an image's metadata from another registry (which finds the digest ID of the image, so that internally you can trigger deployments that use the latest digest ID), OpenShift needs to be able to get the correct digest ID. When Docker 1.10+ tries to push an image, it first

Re: configuring periodic import of images

https://docs.openshift.com/enterprise/3.2/install_config/install/docker_registry.html " The manifest v2 schema 2 (*schema2*) is not yet supported." Sorry :) ​

Re: configuring periodic import of images

It is only in alpha.3 On Aug 11, 2016, at 7:12 PM, Andrew Lau wrote: I'm not sure if it's only in the 1.3.0-alpha3 but https://docs.openshift.org/latest/install_config/install/docker_registry.html#docker-registry-configuration-reference-middleware specifically,

Re: configuring periodic import of images

On Thu, Aug 11, 2016 at 5:15 PM, Tony Saxon wrote: > Damn, I just went through having to downgrade my registry because I was > pushing with 1.12 and openshift (running docker 1.10) wasn't able to pull > the image due the the sha256 hash that it was referencing not existing

Re: configuring periodic import of images

Damn, I just went through having to downgrade my registry because I was pushing with 1.12 and openshift (running docker 1.10) wasn't able to pull the image due the the sha256 hash that it was referencing not existing because of the v1/v2 issues. I guess my only option if I don't want to upgrade my

Re: configuring periodic import of images

If you are using different versions of docker on openshift, and the server where the image was build, you will fall into this (known) problem. Check out https://trello.com/c/CJiUnVUm/136-3-docker-1-10- push-force-schema1-manifest-via-daemon-flag Hopefuly, this seems to be fixed in the upcoming