From d74b5ab49b2b483b1614f5f8ffcfe154de3ccd1b Mon Sep 17 00:00:00 2001 From: Sai Chandu Vallaboju Date: Fri, 24 Jul 2026 09:07:38 -0400 Subject: [PATCH] Clarify Docker webhooks setup --- src/content/docs/docs/standalone/docker.mdx | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/src/content/docs/docs/standalone/docker.mdx b/src/content/docs/docs/standalone/docker.mdx index 18fd14e1..51e43884 100644 --- a/src/content/docs/docs/standalone/docker.mdx +++ b/src/content/docs/docs/standalone/docker.mdx @@ -73,21 +73,18 @@ To mount the current directory use `-v $PWD:/home/wiremock` e.g.: [WireMock extensions](../../extending-wiremock/) are packaged as JAR files. In order to use them they need to be made available at runtime and WireMock must be configured to enable them. -For example, to use the [Webhooks extension](../../webhooks-and-callbacks/) we would first download [wiremock-webhooks-extension-3.13.1.jar](https://repo1.maven.org/maven2/org/wiremock/wiremock-webhooks-extension/3.13.1/wiremock-webhooks-extension-3.13.1.jar) -into the `extensions` directory under our working directory. - -Then when starting Docker we would mount the extensions directory to `/var/wiremock/extensions` and enable the webhooks extension -via a CLI parameter: +Bundled extensions such as [Webhooks](../../webhooks-and-callbacks/) are already included in WireMock `3.1.0+`, so they only need to be enabled via a CLI parameter: ```sh docker run -it --rm \ -p 8080:8080 \ --name wiremock \ - -v $PWD/extensions:/var/wiremock/extensions \ wiremock/wiremock \ --extensions org.wiremock.webhooks.Webhooks ``` +For third-party or custom extensions, download the JAR into the `extensions` directory under your working directory, mount that directory to `/var/wiremock/extensions`, then enable the extension via `--extensions`. If you need the legacy standalone webhooks extension for WireMock `3.0.x` or `2.x`, refer to the [2.x webhooks documentation](https://wiremock.org/2.x/docs/webhooks-and-callbacks/). + ### Building your own image Inside the container, the WireMock uses `/home/wiremock` as the root from which it reads the `mappings` and `__files` directories.