The link to the doc: https://docs.openshift.org/latest/admin_guide/pruning_resources.html
I'm asking because "oadm prune images --confirm" doesn't reduce the size of the registry on our cluster (OS 1.0.6). "oc get images" shows over 100 images from a single pod and they aren't being pruned. Is there hope that this is already fixed in a newer version of OpenShift or will we have to delete the whole registry? I'd be glad to know if you have any ideas about how we could troubleshoot this. Regards, v Am 2016-01-19 um 12:25 schrieb Michalis Kargakis: > By the way, which doc mentions "openshift.io/image.managed > <http://openshift.io/image.managed>" ? > > On Tue, Jan 19, 2016 at 11:57 AM, Michalis Kargakis <[email protected]> > wrote: > > This annotation is added to images that are pushed to the internal > private registry. > That's what `oadm prune images` is for ie. pruning images from the > registry. > > You can run `oadm prune images` w/o --confirm to see which images are > about to be pruned. > You can also `oc get images` and all of your registry images will point > to your registry in the > DOCKER REF column. > > > On Tue, Jan 19, 2016 at 11:01 AM, v <[email protected] > <mailto:[email protected]>> wrote: > > Hello, > > according to the docs "oadm prune images --confirm" will only delete > images with the annotation " openshift.io/image.managed > <http://openshift.io/image.managed>". > > Where does this tag come from and is possible to check whether an > image currently has this tag? > > Regards, > v > > _______________________________________________ > users mailing list > [email protected] > <mailto:[email protected]> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
