OpenShift Registry using S3 storage returns "invalid memory address or nil pointer dereference" error when it is tried to be hard-pruned

Solution In Progress - Updated -


  • The following error message shows up when the built-in OpenShift Container Platform Registry is using an S3 storage backend and is tried to be hard-pruned:
/usr/bin/dockerregistry -prune=check
INFO[0000] start prune (dry-run mode)                    distribution_version=v2.7.1+unknown go.version=go1.16.6
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xde4b1d]


  • Red Hat OpenShift Container Platform 4.x.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content