-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Large output of processes with TTY gets occasionally truncated #3738
Labels
Comments
I'll take a look at this one and see if I can find anything |
crosbymichael
added a commit
to crosbymichael/containerd
that referenced
this issue
Oct 11, 2019
Reized the I/O buffers to align with the size of the kernel buffers with fifos and move the close aspect of the console to key off of the stdin closing. Fixes containerd#3738 Signed-off-by: Michael Crosby <[email protected]>
estesp
pushed a commit
to estesp/containerd
that referenced
this issue
Oct 14, 2019
Reized the I/O buffers to align with the size of the kernel buffers with fifos and move the close aspect of the console to key off of the stdin closing. Fixes containerd#3738 Signed-off-by: Michael Crosby <[email protected]> Signed-off-by: Phil Estes <[email protected]>
erikwilson
pushed a commit
to erikwilson/rancher-containerd
that referenced
this issue
Oct 23, 2019
Reized the I/O buffers to align with the size of the kernel buffers with fifos and move the close aspect of the console to key off of the stdin closing. Fixes containerd#3738 Signed-off-by: Michael Crosby <[email protected]> Signed-off-by: Phil Estes <[email protected]>
dmcgowan
pushed a commit
to thaJeztah/containerd
that referenced
this issue
Nov 19, 2019
* Update the runc vendor to v1.0.0-rc9 which includes an additional mitigation for [CVE-2019-16884](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16884). - More details on the runc CVE in [opencontainers/runc#2128](opencontainers/runc#2128), and the additional mitigations in [opencontainers/runc#2130](opencontainers/runc#2130). * Add local-fs.target to service file to fix corrupt image after unexpected host reboot. Reported in [containerd#3671](containerd#3671), and fixed by [containerd#3745](containerd#3745). * Fix large output of processes with TTY getting occasionally truncated. Reported in [containerd#3738](containerd#3738) and fixed by [containerd#3754](containerd#3754). * Fix direct unpack when running in user namespace. Reported in [containerd#3762](containerd#3762), and fixed by [containerd#3779](containerd#3779). * Update Golang runtime to 1.12.13, which includes security fixes to the `crypto/dsa` package made in Go 1.12.11 ([CVE-2019-17596](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17596)), and fixes to the go command, `runtime`, `syscall` and `net` packages (Go 1.12.12). * Add Windows process shim installer [containerd#3792](containerd#3792) * CRI fixes: - Fix shim delete error code to avoid unnecessary retries in the CRI plugin. Discovered in [containerd/cri#1309](containerd/cri#1309), and fixed by [containerd#3733](containerd#3733) and [containerd#3740](containerd#3740). Signed-off-by: Sebastiaan van Stijn <[email protected]>
tussennet
pushed a commit
to tussennet/containerd
that referenced
this issue
Sep 11, 2020
Reized the I/O buffers to align with the size of the kernel buffers with fifos and move the close aspect of the console to key off of the stdin closing. Fixes containerd#3738 Signed-off-by: Michael Crosby <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Hi containerd,
We (CF Garden) are experiencing occasional container process output being cut out in our CI environment. We managed to reproduce the issue via a unit test
The test loops 100 times exec'ing a process with TTY enabled in a container which prints numbers from 1 to 1000000 to its stdout. The test checks the final numbers are printed. Depending on the runtime we use to run the test with we get the following results:
io.containerd.runtime.v1.linux
) the test would either fail with a process output being cut out, or the process being executed (i.e.seq
) just blocks writing to stdout. In the cases when the test fails we get the following error:io.containerd.runc.v2
) the test would always hang with theseq
process getting stuck writing to stdout.We verified that the issue is available on both master and 1.3.0
cc @kieron-pivotal
The text was updated successfully, but these errors were encountered: