Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Open
iTrooz wants to merge5 commits intocontainers:main
base:main
Choose a base branch
Loading
fromiTrooz:build_output_flag

Conversation

@iTrooz
Copy link

Checklist

Ensure you have completed the following checklist for your pull request to be reviewed:

  • Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
    commits. (git commit -s). (If needed, usegit commit -s --amend). The author email must match
    the sign-off email address. SeeCONTRIBUTING.md
    for more information.
  • Referenced issues usingFixes: #00000 in commit message (if applicable)
  • Tests have been added/updated (or no tests are needed)
  • Documentation has been updated (or no documentation changes are needed)
  • All commits passmake validatepr (format/lint checks)
  • Release note entered in the section below (orNone if no user-facing changes)

Does this PR introduce a user-facing change?

make build flag `--output=tar,dest=-` have correct behaviour (streaming to stdout)print error on build flag `--output=type=INVALID` instead of outputting image to folder `type=INVALID`

Note

I don't believe documentation changes are needed. I may be wrong ?

This PR lays the groundwork for introducingtype=registry, which I will work on when this PR is merged

Signed-off-by: iTrooz <hey@itrooz.fr>
Signed-off-by: iTrooz <hey@itrooz.fr>
Signed-off-by: iTrooz <hey@itrooz.fr>
@openshift-ci
Copy link
Contributor

[APPROVALNOTIFIER] This PR isNOT APPROVED

This pull-request has been approved by:iTrooz
Once this PR has been reviewed and has the lgtm label, please assignluap99 for approval. For more information seethe Code Review Process.

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/approve in a comment
Approvers can cancel approval by writing/approve cancel in a comment

@iTrooz
Copy link
Author

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
Copy link
Member

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 ?

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.

TomSweeneyRedHat reacted with thumbs up emoji

@mheon
Copy link
Member

For when you port this over to buildah: I wonder if a check that/dev/stdout is not a TTY is appropriate? Streaming a tar file to the terminal isn't very useful, so we want to make sure the user is redirecting to a file or piping to another process.

@iTrooz
Copy link
Author

Done !containers/buildah#6476

I wonder if a check that /dev/stdout is not a TTY is appropriate?

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

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@iTrooz@Luap99@mheon

[8]ページ先頭

©2009-2025 Movatter.jp