DOCKER-COMPOSE-EVENTS(1)

πŸ“¦ version 2.26.1, in debian trixie

πŸ’– docker-compose-events β€” bestie's guide to the vibes πŸ’–

okay so this is the manual page for docker-compose-events from the docker-compose fam, and bestie, it's giving real time. it's literally in the DOCKER-COMPOSE-EVENTS(1) manual, and we're about to make it make sense. 🫢


✨ NAME ✨

docker-compose-events β€” Receive real time events from containers 🌸

no cap, that's the whole job. it watches your containers and tells you what they're doing, as they do it. main character energy for real.


πŸŽ€ SYNOPSIS πŸŽ€

docker compose events [OPTIONS] [SERVICE...]

that's it. that's the whole incantation. type it and the tea starts pouring. β˜•


πŸ¦‹ DESCRIPTION πŸ¦‹

Stream container events for every container in the project. every single one. you're not picking and choosing here, it's the whole group chat. πŸ’…

now, the moment you add the --json flag, it switches the vibe: a json object is printed one per line, in this exact format:

{
    "time": "2015-11-20T18:01:03.615550",
    "type": "container",
    "action": "create",
    "id": "213cf7...5fc39a",
    "service": "web",
    "attributes": {
      "name": "application_web_1",
      "image": "alpine:edge"
    }
}

look at that structure. time, type, action, id, service, and an attributes block holding name and image. gorgeous. iconic. no notes. 😭✨

and the events that can be received using this? you can see them here: ⟨/reference/cli/docker/system/events/#object-types⟩. go peek, iykyk. πŸ‘‘


πŸ’… OPTIONS πŸ’…

  • -h, --help[=false] β€” help for events. your lil "wait what does this do again" button. πŸŽ€
  • --json[=false] β€” Output events as a stream of json objects. flip this on when you want machine-readable receipts instead of vibes. πŸ”₯

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

  • --dry-run[=false] β€” Execute command in dry run mode. a lil rehearsal before the real performance, bestie. no actual changes, just practice. 🧚

🌈 SEE ALSO 🌈

  • docker-compose(1) β€” the parent, the blueprint, the origin story. go read it, fr fr. πŸ’œ

🫢 reminder from your girl: every flag, every value, every default above is exactly what the original says. don't @ me with "i thought it was different." it wasn't. periodt. πŸ’…

and that's the whole page, bestie!! this was the docker-compose-events(1) manual, dated Mar 2025, and yeah the footer said DOCKER-COMPOSE-EVENTS(1) too because it loves symmetry. go stream some events, you ate. πŸ’–πŸŒΈβœ¨

πŸ“¦ where this page comes from