-
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 dockerignore, unexpected (wrong) diagnostic #12838
Comments
- reenable git:// tests - git command fails with (EVIL) status 128. Deal with it. - skip two failing tests that I don't know how to fix: a) --unsetenv is not passed on to buildah (should be easy) b) something manifest-related - skip a bunch more podman-remote tests. Filed an issue for one of them (containers#12838), the others may not be fixable. Signed-off-by: Ed Santiago <[email protected]>
- reenable git:// tests - git command fails with (EVIL) status 128. Deal with it. - skip a bunch more podman-remote tests. Filed an issue for one of them (containers#12838), the others may not be fixable. Signed-off-by: Ed Santiago <[email protected]> Signed-off-by: Paul Holzinger <[email protected]>
I'll take a look. Thanks for opening an issue, @edsantiago! |
Ah, OK. Since #8374, the remote client is parsing the ignore files and excludes matches from being tar'ed up. This explains the stat error: the file is really not there. Not sure if we should massage the test OR if we should send the entire context over and let the server exclude the files. |
I think the test should be massaged. |
As long as podman --remote build is doing what is supposed to. |
I am not entirely sure if the context should be pre-processed on the client side. @jwhonce WDYT? |
The issue would then be sending files over that are not needed, so you are wasting bandwidth. But then again, the excludes also have to happen when you call in with the API. |
@vrothberg I put the pre-processing on the client to not waste bandwidth. Otherwise there is the risk of copying a huge file to the server and then ignoring it. @rhatdan podman-py processes the ignores on the client. |
Works for me. |
A friendly reminder that this issue had no activity for 30 days. |
@jwhonce @edsantiago @vrothberg Where are with this one? |
The test is currently disabled in podman: podman/test/buildah-bud/apply-podman-deltas Lines 196 to 197 in c39dffe
Although I have provisions in |
I think we can live with the difference and should close this issue. |
OK |
containers/buildah#3576 added an error message and a test for it. This is failing in podman-remote (not podman).
The error emitted by buildah and regular podman:
The error emitted by podman-remote:
(line breaks added for readability)
The text was updated successfully, but these errors were encountered: