Events
Events answers “what happened last night?”. It lists what Docker recorded about the containers, newest first, from docker events.
Opening it
Section titled “Opening it”Eon the container list: every container of the server.- Events on a container’s Docker tab: that container, or for a Swarm task, every task of its service, so the tasks a redeploy replaced are included.
What it shows
Section titled “What it shows”Each line is one event:
- died, with the exit code explained:
exit 137 (killed: out of memory or SIGKILL),exit 143 (stopped with SIGTERM); - out of memory;
- killed, with the signal;
- restarted, started, stopped;
- unhealthy, when a healthcheck failed.
Problems are marked ×: an exit other than 0, out of memory and unhealthy. The title counts them.
| Key | Action |
|---|---|
b |
Problems only, or every event |
t |
The last 24 hours (the default), 1 hour or 7 days |
r |
Read again |
How far back it goes
Section titled “How far back it goes”Docker keeps only its last 256 events in memory. When that buffer is full, the screen says “Docker keeps its last 256 events: older ones are gone”. On a busy server the 7-day view may then start later than 7 days ago.