-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
never send procError after the socket closed #4173
Conversation
@lifubang can we add an integration test for this? So the next refactor doesn't regress on this. |
7a237e2
to
8071b9a
Compare
Good idea, added two tests. Thanks. |
8071b9a
to
1f6f980
Compare
1f6f980
to
7730c81
Compare
417ca41
to
1c3b067
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think atomic.Bool is nicer for this than using mutexes, but I don't have a strong opinion.
e92ac5d
to
79f3d6a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, sorry for the nitpicks
Signed-off-by: lifubang <lifubang@acmcoder.com>
Signed-off-by: lfbzhm <lifubang@acmcoder.com>
79f3d6a
to
0bc4732
Compare
We have moved the error msg display position in #3385, I think it's reasonable to display the container init msg in one place, but in this PR, we changed an error ignore behavior in https://github.com/opencontainers/runc/blob/main/libcontainer/init_linux.go#L112-L113 .
Yes, we should display the error before
procReady
has sent, but we should ignore after that. So I think we can add a field to indicate whether we have sentprocReady
or not in child process. It's not needed for the parent process, but we can reuse it to remove a local varseenProcReady
.Fix #4171