[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: prune images error - 503

Upon pruning images this command reaches out to registry to actually
remove them from there. Apparently, it has has problems reaching out
to your registry. There are two flags you might want to check out
--certificate-authority - which points to a CA when self-signed cert is used
--registry-url - to specify which registry to talk to.

Additionally you can increase the verbosity (--loglevel=7) and see the communication
between oadm prune images and the server, including the registry. If still experiencing
problems, please lemme know with that logs attached, so I could help more.


On Tue, Oct 25, 2016 at 9:29 AM, Lionel Orellana <lionelve gmail com> wrote:

I'm trying to run 

oadm prune images --keep-tag-revisions=3 --keep-younger-than=24h --confirm 

but after a while I get 

error: error communicating with registry: unexpected status code 503

I am able to prune builds and deployments. prune images without --confirm also returns Ok. 

I've been building a ~6GB image repeatedly in the last couple of days. Seems like it's struggling to delete some of those? 



users mailing list
users lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]