Containerfile.in not automatically pre-processed about podman HOT 2 CLOSED

I am not sure if adding yet two more location that are checked by default are so useful.

I would argue we should just make the docs more clear.

For this document, a file referred to as a Containerfile can be a file named either 'Containerfile' or 'Dockerfile'.

So there is that already. However the docs never really say how the default context directory is "searched"

from podman.

However the docs never really say how the default context directory is "searched"

For a "Docs fix", I think it should specify that and that the -f argument is required to take advantage of Containerfile.in. I'm not a big fan, but I think this would be an acceptable short-term solution. Perhaps fixing the search could then be an RFE.

OTOH, in terms of POLA, I think there's little merit to an argument for a "just works" search here. Something like: Containerfile.in -> Containerfile -> Dockerfile.

I think users DO expect features like this to not require extra arguments, documented or not. Nobody "wants" to have to go RTFM when something doesn't work the simple way. They want the developers to have anticipated their needs/desires (to a reasonable extent) accordingly.

from podman.