-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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-remote build, with '*' in .dockerignore: overzealously ignores Dockerfile #9867
Comments
@vrothberg @nalind This I guess is an issue with the copier, where we should special case Containerfile and Dockerfile to not be ignored when * is specified. @edsantiago did you try this out on Docker? |
I didn't. I'm |
Sadly I still have it installed, for just this type of occurrance, and yes it works on Docker. |
I don't see the |
Volunteering? |
I am usually volunteered :^) Pipeline is long but we crossed the 200 issues threshold :) |
A friendly reminder that this issue had no activity for 30 days. |
Still present. |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
This works for me with the latest in the main branch. |
It actually doesn't work. I suspect you shortcutted my reproducer above, running |
If the user specifies "*" in a .dockerignore or a .containerignore then podman-remote build should not exclude the Dockerfile or Containerfile or any content pointed to by `-f` in the context directory. We still need these files on the server side to complete the build. Fixes: containers#9867 Signed-off-by: Daniel J Walsh <[email protected]>
Setup:
In window 2:
Regular (non-remote) podman works fine, presumably because it doesn't do the interim copy of the context dir to $TMPDIR:
The text was updated successfully, but these errors were encountered: