Misleading error message when building a nonexistent Containerfile #22940
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
remote
Problem is in podman-remote
Issue Description
When running a build from a context that does not include a Containerfile, users get a friendly error message. However, when attempting to run a nonexistent Containerfile, users get an error message referencing a path in
/var/tmp
. This may be a quirk of running Podman on MacOS based on underlying volume mount details, since Podman is actually running inside a VM.Steps to reproduce the issue
I'm running Podman on MacOS, installed via Homebrew.
When attempting to build from a context where there is no Containerfile, users get a nice error message:
However, when doing the same using a Containerfile specified using
-f
, we get different output:To reproduce, simply run this on MacOS:
podman build -f foo
where the filefoo
does not exist.Describe the results you received
The error message references a path that the user knows nothing about:
Describe the results you expected
I expected an error message in my home directory, for example:
Or, perhaps better, a friendly error message modeling the one that appears when running
podman build .
from a context that does not include a Containerfile:podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Running on MacOS installed via Homebrew
Running the latest
podman machine
image:Additional information
I only tested on MacOS and my guess is that this is specific to non-Windows OSes.
The text was updated successfully, but these errors were encountered: