Nuke the new nixery image

[edsantiago]

Registry has been down for a day. This is blocking all CI.

Switch to $SAFEIMAGE, our quay.io testimage.

Signed-off-by: Ed Santiago [email protected]

None

[packit-as-a-service]

Ephemeral COPR build failed. @containers/packit-build please check.

[flouthoc]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: edsantiago, flouthoc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [flouthoc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[edsantiago]

@nalind PTAL. I have a bad feeling that the reason this PR is passing is because the test is not actually a test. That is, that there is something magical about the nixery image that causes this test to fail, but there is no actual testing anywhere in the test to verify that this magical attribute exists in the image being tested.

nixery is back up, and I've pulled the image, and I'll try to figure out what is so special about it, but your help would be most appreciated.

[edsantiago]

nixery is back up, so here are my findings:

1. The magic attribute that we're looking for seems to be:

$ podman inspect nixery.dev/shell:latest --format '{{.History}}'
[]

(i.e., empty "History" field)

2. buildah 1.34.1 does not manifest the bug, but I checked out 8098bf2 , built it, and the new bud-implicit-no-history test fails as follows:

...
[2/2] COMMIT
Error: committing container for step {...}: \
    copying layers and metadata for container "SHA": \
    initializing source containers-storage:6164d56ff2d5-working-container: \
    internal error: history lists 2 non-empty layers, but we have 13 layers on disk

What I would like to do now is craft a custom image with this same History attribute. Preferably something we can craft inline in the test itself, but at least something we can store on quay. @nalind, I could figure that out eventually, but if you have any advice on how to do that I would hugely appreciate it.

[nalind]

There's a patch in #5473 that crafts a suitable image to get around this.