Skip to content
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

imagebuildah: disable pseudo-terminals for RUN #2803

Merged
merged 1 commit into from
Nov 17, 2020

Conversation

nalind
Copy link
Member

@nalind nalind commented Nov 17, 2020

What type of PR is this?

/kind bug

What this PR does / why we need it:

Always handle RUN instructions with no pseudo terminal, which matches what I see with docker build 19.03. Interactive buildah run will still have the same default behavior.

How to verify it

Tests should continue to pass, and the issue described in containers/podman#8342 should no longer occur.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

RUN instructions in builds will no longer be run attached to a pseudo-terminal.

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Nov 17, 2020
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nalind

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

Always handle RUN instructions with no pseudo terminal, which matches
what I see with docker build 19.03.  Interactive 'buildah run' will
still have the same default behavior.

Signed-off-by: Nalin Dahyabhai <[email protected]>
@nalind nalind added todo-backport-to-1.16 We should do or consider a backport to 1.16. Remove when we either decide not to, or open a PR. todo-backport-to-1.17 We should do or consider a backport to 1.17. Remove when we either decide not to, or open a PR. todo-backport-to-1.18 We should do or consider a backport to 1.18. Remove when we either decide not to, or open a PR. labels Nov 17, 2020
@rhatdan
Copy link
Member

rhatdan commented Nov 17, 2020

LGTM

1 similar comment
@TomSweeneyRedHat
Copy link
Member

LGTM

@TomSweeneyRedHat
Copy link
Member

/lgtm

@openshift-merge-robot openshift-merge-robot merged commit 60813b5 into containers:master Nov 17, 2020
@nalind nalind deleted the bud-no-terminal branch November 17, 2020 18:31
@nalind nalind removed the todo-backport-to-1.18 We should do or consider a backport to 1.18. Remove when we either decide not to, or open a PR. label Jan 6, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved kind/bug Categorizes issue or PR as related to a bug. lgtm locked - please file new issue/PR todo-backport-to-1.16 We should do or consider a backport to 1.16. Remove when we either decide not to, or open a PR. todo-backport-to-1.17 We should do or consider a backport to 1.17. Remove when we either decide not to, or open a PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants