Ifeoma

The thing that keeps this hidden: emulation does not announce itself. The container runs, the tests pass, everything is correct, it is just slow, and slow gets attributed to the machine or the job or the day.

Check the image architecture rather than reasoning about it. If one image in your set was built for a different architecture from the rest, that is your forty minutes, and it is usually a base image somebody pinned by digest two years ago.

Multi-architecture images fix it properly, if you control the build. If you do not, pinning a matching tag is the short version.

That comparison is the diagnostic, really. It rules out most of what people check first.