-
Notifications
You must be signed in to change notification settings - Fork 1.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
-pass-fd does not allow specifying container descriptors 1 or 2 #11349
Comments
I believe |
Incorrect comment, deleted. |
Flaky on my machine too. But also I don't understand what is going on there. This command you posted is not supposed to print anything to stderr, because we have redirected the stderr of outer command to 9. |
It is even funnier. The command I mentioned initially
in about 1 in 20 invocations actually does redirect container stderr into the descriptor 9 (does not print into stderr, but output gets into the file). |
The issue about non-determinism: #11350. |
I think this issue is a duplicate of #11350, because redirect
This command 100% of time redirects to a provided descriptor. |
Description
Open a file descriptor:
(empty as expected)
Passing file descriptor 5, works correctly:
Passing file descriptor 2: identical command, but 2 instead of 5:
Stderr is forwarded to
runsc
stderr rather than into provided file descriptor.Update: the last command is actually flaky: in about 1 in 20 invocations redirect actually happens.
Use case
Separate error messages from the
runsc
itself, and from the process inside the container. For example, one can be shown in UI, and another only sent to logs.Is this feature related to a specific bug?
No response
Do you have a specific solution in mind?
Either:
The text was updated successfully, but these errors were encountered: