Make registry tests using docker.socket dockerless

[miminar]

The tests using the docker socket fail because the access is not granted anymore in pods.
Therefore they are now being marked with [local].

This issue is a reminder to rewrite the tests in a dockerless way.

See the related discussion:

• Registry catalog image-registry#87 (comment)

And related [local] PRs:

• mark tests that use docker socket as [local] #20077
• mark hard prune extended test as local only for now #20061

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[bparees]

/lifecycle frozen
/remove-lifecycle stale

/assign @dmage

This is more urgent than before as these tests are not being run anywhere anymore i do not believe, until we remove the local tag.

[bparees]

might be possible to use oc image mirror to push an image from docker hub into the registry for these tests, too.

[gitsan13]

I would like to contribute to this issue. Kindly guide me through the steps as I am a newbie in this field.

[dmage]

@gitsan13 one set of tests that are marked as [Local] is here:

origin/test/extended/images/prune.go

Line 34 in e8d48e3

var _ = g.Describe("[sig-imageregistry][Feature:ImagePrune][Serial][Suite:openshift/registry/serial][Local] Image prune", func() {

But it's a pretty tricky issue. Why did you choose it? Before you start working on any test, you need to get a working OpenShift or OKD cluster and learn how to run tests. This alone can be overwhelming.