-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Docker/podman difference when piping to exec statement #4785
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/bug
Categorizes issue or PR as related to a bug.
label
Jan 3, 2020
it seems crun is correctly passing down stdin. It might be conmon, @haircommander is it something we support in conmon now? |
I think it might be exec ignoring -t and using a terminal unconditionally.
I believe that Docker will show identical behavior if -t is passed.
…On Sun, Jan 5, 2020, 04:02 Giuseppe Scrivano ***@***.***> wrote:
it seems crun is correctly passing down stdin.
It might be conmon, @haircommander <https://github.com/haircommander> is
it something we support in conmon now?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4785>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCDHXUAX7HGGTAX2G3DQ4GO2PANCNFSM4KCTCUPQ>
.
|
Merged
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Jan 9, 2020
- run: --name (includes 'podman container exists' tests) - run: --pull (always, never, missing) - build: new test for ADD URL (containers#4420) - exec: new test for issue containers#4785 (pipe getting lost) - diff: new test - selinux (mostly copied from docker-autotest) Plus a bug fix: the wait_for_output() helper would continue checking, eventually timing out, even if the container had already exited (probably because of an error). Fix: as part of the loop, run 'podman inspect' and bail out if container is not running. Include exit code and logs. Signed-off-by: Ed Santiago <santiago@redhat.com>
Merged
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Jan 9, 2020
- run: --name (includes 'podman container exists' tests) - run: --pull (always, never, missing) - build: new test for ADD URL (containers#4420) - exec: new test for issue containers#4785 (pipe getting lost) - diff: new test - selinux (mostly copied from docker-autotest) Plus a bug fix: the wait_for_output() helper would continue checking, eventually timing out, even if the container had already exited (probably because of an error). Fix: as part of the loop, run 'podman inspect' and bail out if container is not running. Include exit code and logs. Signed-off-by: Ed Santiago <santiago@redhat.com>
edsantiago
added a commit
to edsantiago/libpod
that referenced
this issue
Jan 13, 2020
- run: --name (includes 'podman container exists' tests) - run: --pull (always, never, missing) - build: new test for ADD URL (containers#4420) - exec: new test for issue containers#4785 (pipe getting lost) - diff: new test - selinux (mostly copied from docker-autotest) Plus a bug fix: the wait_for_output() helper would continue checking, eventually timing out, even if the container had already exited (probably because of an error). Fix: as part of the loop, run 'podman inspect' and bail out if container is not running. Include exit code and logs. Signed-off-by: Ed Santiago <santiago@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 23, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Piping to stdin of a
podman exec
statement behaves differently from piping todocker exec
Steps to reproduce the issue:
Open a second terminal and type
note the output
abc
Open a second terminal and type
note the absence of any output
Describe the results you received:
Stdin doesn't seem to get piped to
podman exec
's argument statement, whereas it does seem to get piped todocker exec
's argument statement. This doesn't follow from the example above, but more complex cases, like piping a database dump to a database, and the database not having been altered in thepodman
case, would suggest this.Describe the results you expected:
I would have expected
podman
anddocker
to behave in the same wayAdditional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora 31 running on hardware.
The text was updated successfully, but these errors were encountered: