Inheritance diagram for DockerSdk.Containers.Events.ContainerStopCompletedEvent:
Additional Inherited Members | |
 Properties inherited from DockerSdk.Containers.Events.ContainerEvent | |
| ContainerFullId | ContainerId [get] |
| Gets the container's ID. More... | |
| ContainerName? | ContainerName [get] |
| Gets the container's name, if it was included in the event details. More... | |
| ContainerEventType | EventType [get] |
| Gets the type of event that this is. More... | |
| ImageReference? | ImageReference [get] |
| Gets a reference to the container's image, if it was included in the event details. More... | |
| Properties inherited from DockerSdk.Events.Event | |
| EventSubjectType | SubjectType [get] |
| DateTimeOffset | Timestamp [get] |
| Gets the date and time at which the event occurred, in UTC, per the daemon's clock. More... | |
| Properties inherited from DockerSdk.Events.IEventLowLevel | |
| EventSubjectType | SubjectType [get] |
| Gets a value indicating what type of thing the event is about. More... | |
| string | ActorId [get] |
| Gets the full ID of the event's subject. More... | |
| string | Action [get] |
| Gets a value indicating the type of event this is. More... | |
| IReadOnlyDictionary< string, string > | ActorDetails [get] |
| Gets a dictionary of supplementary information provided by the daemon about the event's subject. The keys that appear here vary by subject type, event type, and the specifics of the subject. More... | |
| DateTimeOffset | Timestamp [get] |
| Gets the date and time at which the event occurred, in UTC, per the daemon's clock. More... | |
Detailed Description
Indicates that Docker has finished performing a "stop" operation, either on its own or in the first half of a restart operation.
If you're only interested in state changes, and not which specific command caused them, it may be best to simply ignore this event type, since it's always preceded by ContainerExitedEvent anyway.
Docker "kill" commands do not emit this event; however, the presence of this command does not necessarily mean that the process shut down gracefully. In particular, if someone performs a "stop" operation on a paused container, it appears that the container will be only briefly unpaused before it's forcibly shut down. (Sequence of events: signal 15, unpause, signal 9, exit stop.)
The documentation for this class was generated from the following file:
- Containers/Events/ContainerStopCompletedEvent.cs
