-
Notifications
You must be signed in to change notification settings - Fork 18.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
docker event for exec_die #35702
Comments
Discussing this in the maintainers meeting, and we think adding these events make sense. There is some discussion around order of events for Are you interested in implementing this? |
Yes, thanks ! |
I'm not worried about the arrival order, could just be documented not to be guaranteed if there's a risk for some race condition. |
See moby/moby#35702 for more information about the event.
Description
As a container terminate by itself (main PID 1 process complete) an
container die
event is reported with exit code.As an exec process completes, docker inspect do report updated
ExecIDs
set but no event is logged. As a result, one only can monitor exec completion by polling. Ancontainer exec_die
event would allow an asynchronous implementation.My actual use case is to run build processes in an existing containers from a Jenkins plugin. I'd like to avoid polling this container for exec completion.
Steps to reproduce the issue:
docker event
sleep 100
Describe the results you received:
logged events:
Describe the results you expected:
logged events:
The text was updated successfully, but these errors were encountered: