Skip to content

WUD (What's up Docker)

WUD watches your containers’ images for new versions. Its HTTP trigger can send each update it finds to InfraInbox, where it waits in the inbox with the rest of your infrastructure’s news.

Tested with: built from WUD 9’s container model; not yet run against a live WUD.

Each container with an update available arrives as one info event, such as Update available: immich-server v2.1.0 → v2.2.0, with a link to the release notes when WUD has one. An update is news, not a fault, so it opens no incident and notifies no one unless you add a routing rule for the wud.update type.

  • WUD with its HTTP trigger available (every release has it), able to reach your InfraInbox server.
  1. Go to Add source → WUD and name it. InfraInbox issues an ingest key, shown once, with the settings below filled in.

  2. Add these to WUD’s environment (in its Compose file, say) and restart it:

    Terminal window
    WUD_TRIGGER_HTTP_INFRAINBOX_URL=https://infrainbox.example.com/hooks/wud
    WUD_TRIGGER_HTTP_INFRAINBOX_AUTH_TYPE=BEARER
    WUD_TRIGGER_HTTP_INFRAINBOX_AUTH_BEARER=iik_src_…
  3. Optionally add WUD_TRIGGER_HTTP_INFRAINBOX_BATCH=true to send one request per scan instead of one per container.

The same settings, with a placeholder where the key goes, stay on the source’s Connect tab.

Run a container on an older tag of an image with a newer one available. After WUD’s next scan, an info event appears on the source’s Events tab.

  • Routing rules — get notified about major updates, or about specific containers