from small one page howto to huge articles all in one place

search text in:




Other .linuxhowtos.org sites:gentoo.linuxhowtos.org



Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

209586

userrating:


May 25th. 2007:
Words

486

Views

258592

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

149883

userrating:


April, 26th. 2006:

Druckversion
You are here: manpages





DOCKER

Section: Docker User Manuals (1)
Updated: Jun 2025
Index Return to Main Contents

 

NAME

docke-syste-events- Get real time events from the server

 

SYNOPSIS

docker system events [OPTIONS]

 

DESCRIPTION

Get event information from the Docker daemon. Information can include historical information and rea-time information.

Docker containers will report the following events:

attach, commit, copy, create, destroy, detach, die, exec_create, exec_detach, exec_start, export, kill, oom, pause, rename, resize, restart, start, stop, top, unpause, update

Docker images report the following events:

delete, import, load, pull, push, save, tag, untag

Docker volumes report the following events:

create, mount, unmount, destroy

Docker networks report the following events:

create, connect, disconnect, destroy

 

OPTIONS

The -since and -until parameters can be Unix timestamps, date formatted timestamps, or Go duration strings supported by ParseDuration [la]https://pkg.go.dev/time#ParseDuration[ra] (e.g. 10m, 1h30m) computed relative to the client machine's time. If you do not provide the -since option, the command returns only new and/or live events. Supported formats for date formatted time stamps include RFC3339Nano, RFC3339, 200-0-02T15:04:05, 200-0-02T15:04:05.999999999, 200-0-02T07:00, and 200-0-02. The local timezone on the client will be used if you do not provide either a Z or a -00:00 timezone offset at the end of the timestamp. When providing Unix timestamps enter seconds[.nanoseconds], where seconds is the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap seconds (aka Unix epoch or Unix time), and the optional .nanoseconds field is a fraction of a second no more than nine digits long.

 

EXAMPLES

 

Listening for Docker events

After running docker events a container 786d698004576 is started and stopped (The container name has been shortened in the output below):

# docker events 201-0-28T20:21:31.00000000-08:00 59211849bc10: (from whenry/testimage:latest) start 201-0-28T20:21:31.00000000-08:00 59211849bc10: (from whenry/testimage:latest) die 201-0-28T20:21:32.00000000-08:00 59211849bc10: (from whenry/testimage:latest) stop

 

Listening for events since a given date

Again the output container IDs have been shortened for the purposes of this document:

# docker events-since '201-0-28' 201-0-28T20:25:38.00000000-08:00 c21f6c22ba27: (from whenry/testimage:latest) create 201-0-28T20:25:38.00000000-08:00 c21f6c22ba27: (from whenry/testimage:latest) start 201-0-28T20:25:39.00000000-08:00 c21f6c22ba27: (from whenry/testimage:latest) create 201-0-28T20:25:39.00000000-08:00 c21f6c22ba27: (from whenry/testimage:latest) start 201-0-28T20:25:40.00000000-08:00 c21f6c22ba27: (from whenry/testimage:latest) die 201-0-28T20:25:42.00000000-08:00 c21f6c22ba27: (from whenry/testimage:latest) stop 201-0-28T20:25:45.00000000-08:00 c21f6c22ba27: (from whenry/testimage:latest) start 201-0-28T20:25:45.00000000-08:00 c21f6c22ba27: (from whenry/testimage:latest) die 201-0-28T20:25:46.00000000-08:00 c21f6c22ba27: (from whenry/testimage:latest) stop

The following example outputs all events that were generated in the last 3 minutes, relative to the current time on the client machine:

# docker events-since '3m' 201-0-12T11:51:30.999999999Z07:00 4386fb97867d: (from ubuntu:24.04) die 201-0-12T15:52:12.999999999Z07:00 4386fb97867d: (from ubuntu:24.04) stop 201-0-12T15:53:45.999999999Z07:00 7805c1d35632: (from redis:7.2) die 201-0-12T15:54:03.999999999Z07:00 7805c1d35632: (from redis:7.2) stop

If you do not provide the-since option, the command returns only new and/or live events.

 

Format

If a format (-format) is specified, the given template will be executed instead of the default format. Go's text/template package describes all the details of the format.

# docker events-filter 'type=container'-format 'Type={{.Type}} Status={{.Status}} ID={{.ID}}' Type=container Status=create ID=2ee349dac409e97974ce8d01b70d250b85e0ba8189299c126a87812311951e26 Type=container Status=attach ID=2ee349dac409e97974ce8d01b70d250b85e0ba8189299c126a87812311951e26 Type=container Status=start ID=2ee349dac409e97974ce8d01b70d250b85e0ba8189299c126a87812311951e26 Type=container Status=resize ID=2ee349dac409e97974ce8d01b70d250b85e0ba8189299c126a87812311951e26 Type=container Status=die ID=2ee349dac409e97974ce8d01b70d250b85e0ba8189299c126a87812311951e26 Type=container Status=destroy ID=2ee349dac409e97974ce8d01b70d250b85e0ba8189299c126a87812311951e26

If a format is set to {{json .}}, the events are streamed as valid JSON Lines. For information about JSON Lines, refer to https://jsonlines.org .

# docker events-format '{{json .}}' {"status":"create","id":"196016a57679bf42424484918746a9474cd905dd993c4d0f4.. {"status":"attach","id":"196016a57679bf42424484918746a9474cd905dd993c4d0f4.. {"Type":"network","Action":"connect","Actor":{"ID":"1b50a5bf755f6021dfa78e.. {"status":"start","id":"196016a57679bf42424484918746a9474cd905dd993c4d0f42.. {"status":"resize","id":"196016a57679bf42424484918746a9474cd905dd993c4d0f4..

 

Filters

$ docker events-filter 'event=stop' 201-0-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:24.04) 201-0-03T17:42:14.999999999Z07:00 container stop 7805c1d35632 (image=redis:7.2)

$ docker events-filter 'image=ubuntu:24.04' 201-0-10T17:42:14.999999999Z07:00 container start 4386fb97867d (image=ubuntu:24.04) 201-0-10T17:42:14.999999999Z07:00 container die 4386fb97867d (image=ubuntu:24.04) 201-0-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:24.04)

$ docker events-filter 'container=7805c1d35632' 201-0-10T17:42:14.999999999Z07:00 container die 7805c1d35632 (image=redis:7.2) 201-0-03T15:49:29.999999999Z07:00 container stop 7805c1d35632 (image= redis:7.2)

$ docker events-filter 'container=7805c1d35632'-filter 'container=4386fb97867d' 201-0-03T15:49:29.999999999Z07:00 container die 4386fb97867d (image=ubuntu:24.04) 201-0-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:24.04) 201-0-10T17:42:14.999999999Z07:00 container die 7805c1d35632 (image=redis:7.2) 201-0-03T15:49:29.999999999Z07:00 container stop 7805c1d35632 (image=redis:7.2)

$ docker events-filter 'container=7805c1d35632'-filter 'event=stop' 201-0-03T15:49:29.999999999Z07:00 container stop 7805c1d35632 (image=redis:7.2)

$ docker events-filter 'type=volume' 201-1-23T21:05:28.136212689Z volume create tes-even-volum-local (driver=local) 201-1-23T21:05:28.383462717Z volume mount tes-even-volum-local (read/write=true, container=562fe10671e9273da25eed36cdce26159085ac7ee6707105fd534866340a5025, destination=/foo, driver=local, propagation=rprivate) 201-1-23T21:05:28.650314265Z volume unmount tes-even-volum-local (container=562fe10671e9273da25eed36cdce26159085ac7ee6707105fd534866340a5025, driver=local) 201-1-23T21:05:28.716218405Z volume destroy tes-even-volum-local (driver=local)

$ docker events-filter 'type=network' 201-1-23T21:38:24.705709133Z network create 8b111217944ba0ba844a65b13efcd57dc494932ee2527577758f939315ba2c5b (name=tes-even-networ-local, type=bridge) 201-1-23T21:38:25.119625123Z network connect 8b111217944ba0ba844a65b13efcd57dc494932ee2527577758f939315ba2c5b (name=tes-even-networ-local, container=b4be644031a3d90b400f88ab3d4bdf4dc23adb250e696b6328b85441abe2c54e, type=bridge)

$ docker events-filter 'type=plugin' (experimental) 201-0-25T17:30:14.825557616Z plugin pull ec7b87f2ce84330fe076e666f17dfc049d2d7ae0b8190763de94e1f2d105993f (name=tiborvass/sampl-volum-plugin:latest) 201-0-25T17:30:14.888127370Z plugin enable ec7b87f2ce84330fe076e666f17dfc049d2d7ae0b8190763de94e1f2d105993f (name=tiborvass/sampl-volum-plugin:latest)

 

OPTIONS

-f, -filter=         Filter output based on conditions provided

-format=""         Format output using a custom template:
'json': Print in JSON format 'TEMPLATE': Print output using the given Go template. Refer to https://docs.docker.com/go/formatting/ for more information about formatting output with templates

-since=""         Show all events created since timestamp

-until=""         Stream events until this timestamp

 

SEE ALSO

docke-system(1)


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
EXAMPLES
Listening for Docker events
Listening for events since a given date
Format
Filters
OPTIONS
SEE ALSO





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2025 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 12.6 ms