-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman build with relative path to dockerfile in subdirectory fails with "no such file or directory" on Mac #12841
Comments
@cdoern Would you have time to knock this out quick? |
sure, I will take a look |
podman build always finds the abs path but was never using it for the containerfile path. This was causing the remote client to be given a relative path that does not exist. Switch to evaluating and using absolute paths only. resolves containers#12841 Signed-off-by: cdoern <cdoern@redhat.com>
Hello, |
No that should be allowed. |
Hello @rhatdan, With a simple dockerfile like that :
With the command :
If it's not normal I can open a new issue. Thanks in advance :) |
What version of Podman? I think this is fixed in podman 4.0. This is remote podman (podman on a Mac). |
Which you almost certainly do not have yet. RC3 was released today, but you need it on the server as well as the client. |
Only on local mode with a Maxbook air M1 |
Yup have to wait for next release. |
Thanks :) Do you have any release date ? |
Some time in the next few weeks. |
This is the exact same problem that I have on my windows 11 Devkit ARM machine and I have the latest podman version 4.4.4 I can provide more info here or should I create a new ticket? |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Running
podman build
with a relative path to a Dockerfile in a subdirectory fails.docker build
works fine in this case.Steps to reproduce the issue:
podman build -f ./test/Docker .
Describe the results you received:
Error: stat /var/tmp/libpod_builder389648463/build/test/test/Dockerfile: no such file or directory
Describe the results you expected:
successful build
Additional information you deem important (e.g. issue happens only occasionally):
Providing an absolute path works.
podman build -t test -f $PWD/test/Dockerfile .
Docker works fine with relative paths.
docker build -t test -f ./test/Dockerfile .
Here's a screenshot (with successful operations killed so it fits on one screen)
![Screenshot 2022-01-13 at 11 06 01](./?url=aHR0cHM6Ly91c2VyLWltYWdlcy5naXRodWJ1c2VyY29udGVudC5jb20vMTY4OTYwNTMvMTQ5MzE5MDc4LTE2YTVlZDY5LTQ1NTktNDU4ZS1hYjNmLThhNjM3ZTFlMDA0Yy5wbmc=&__proxy_form=0)
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
MacOS 10.15.7 Catalina
The text was updated successfully, but these errors were encountered: