[jeroenhd]

You can inspect the layers of a Docker image. Tools like dive[0] provide a quick and easy way to navigate through the different components your image of choice is made up of.

In terms of functionality once the container is running, you'll have to put some amount of trust into the project maintainers, no more or less than the trust you need om amd64. For containers repackaged by third parties that's quite a pain, but in most cases you can get by just fine with the official container.

If your container of choice has been made by someone real fancy, you may be able to get reproducible builds for all the files inside the container. That would verify that the source and the binary match (though container metadata may not, so a direct image compare would be challenging).

[0]: https://github.com/wagoodman/dive

[pjmlp]

Dive seems to have been abandoned though.

I used it a few times in the past.

[rendaw]

Does it no longer work? I thought I used it just fine a couple weeks ago.

[pjmlp]

It still works, until there are OCI updates that it can't handle, and there are a couple of occasional bugs, depending on the image.