Well I have a Containerfile which resides in a subfolder ./my_app, for docker-compose spec file I simply declare the context: ./my_app and dockerfile: Containerfile. However for buildah-build action, I have to declare the full path for containerfiles: ./my_app/Containerfile. That behaviour caught me by surprise... so wondering if such decision is deliberate or simply it is just an oversight from the onset. Many thanks
Question
Well I have a Containerfile which resides in a subfolder
./my_app
, for docker-compose spec file I simply declare thecontext: ./my_app
anddockerfile: Containerfile
. However for buildah-build action, I have to declare the full path forcontainerfiles: ./my_app/Containerfile
. That behaviour caught me by surprise... so wondering if such decision is deliberate or simply it is just an oversight from the onset. Many thanks