- Notifications
You must be signed in to change notification settings - Fork2.9k
feat(build): make--output=tar,dest=- work + print error on build flag--output=type=INVALID#27436
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
Signed-off-by: iTrooz <hey@itrooz.fr>
Signed-off-by: iTrooz <hey@itrooz.fr>
Signed-off-by: iTrooz <hey@itrooz.fr>
[APPROVALNOTIFIER] This PR isNOT APPROVED This pull-request has been approved by:iTrooz The full list of commands accepted by this bot can be foundhere. Needs approval from an approver in each of these files: Approvers can indicate their approval by writing |
iTrooz commentedNov 4, 2025
I assume this change should be submitted againsthttps://github.com/containers/buildah instead. But where am I supposed to put tests ? Should they stay in this repository ? |
Luap99 commentedNov 4, 2025
https://github.com/containers/buildah/blob/main/tests/bud.bats for example. Givent he same build command is eposed in buildah you should be able to to just add tests there. Once that is merged in buildah and we updated buildah here we can still have like one or two cases to validate that podman produces the same expected errors. |
mheon commentedNov 4, 2025
For when you port this over to buildah: I wonder if a check that |
iTrooz commentedNov 5, 2025
Done !containers/buildah#6476
Probably, especially since docker does it. I could submit this in a separate PR, but I'd like to keep this one focused on this |
Checklist
Ensure you have completed the following checklist for your pull request to be reviewed:
commits. (
git commit -s). (If needed, usegit commit -s --amend). The author email must matchthe sign-off email address. SeeCONTRIBUTING.md
for more information.
Fixes: #00000in commit message (if applicable)make validatepr(format/lint checks)Noneif no user-facing changes)Does this PR introduce a user-facing change?
Note
I don't believe documentation changes are needed. I may be wrong ?
This PR lays the groundwork for introducing
type=registry, which I will work on when this PR is merged