docs: update Docker commands for consistency and simplification

nashjain · nashjain · commit ed7101da5eb7 · 2026-02-06T21:36:47.000+05:30
diff --git a/docs/contract_driven_development/generating_api_specifications.mdx b/docs/contract_driven_development/generating_api_specifications.mdx
@@ -25,7 +25,7 @@ OR
 
 Using docker:
 ```shell
-docker run -p 9000:9000 -v "$PWD/specification:/specification" specmatic/specmatic proxy --target=https://dummyjson.com /specification
+docker run -p 9000:9000 -v "$(pwd)/specification:/specification" specmatic/specmatic proxy --target=https://dummyjson.com /specification
 ```
 
 You will get following confirmation message: <br /> `Proxy server is running on http://localhost:9000. Ctrl + C to stop.`
diff --git a/docs/supported_protocols/arazzo.mdx b/docs/supported_protocols/arazzo.mdx
@@ -182,7 +182,7 @@ In Specmatic Studio, you can start a mock workflow session to simulate end-to-en
 You can also run workflow mocking through the CLI using the mock command from the Specmatic-Arazzo Docker image:
 
 ```shell
-docker run -v "$(pwd):/usr/src/app" specmatic/enterprise mock --spec-file "<workflow.arazzo.yaml>"
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise mock --spec-file "<workflow.arazzo.yaml>"
 ```
 
 ## Sample Projects
diff --git a/docs/supported_protocols/asyncapi/active-mq.mdx b/docs/supported_protocols/asyncapi/active-mq.mdx
@@ -145,7 +145,7 @@ Start your application that implements the AsyncAPI specification. The applicati
 Execute the contract tests using the Specmatic Docker image:
 
 ```bash
-docker run --network host -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" -v "$PWD/spec:/usr/src/app/spec" specmatic/enterprise test
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 Specmatic-async will:
diff --git a/docs/supported_protocols/asyncapi/aws-event-bridge.mdx b/docs/supported_protocols/asyncapi/aws-event-bridge.mdx
@@ -228,7 +228,7 @@ Start your application that implements the AsyncAPI specification. The applicati
 Execute the contract tests using the Specmatic Docker image:
 
 ```bash
-docker run --network host -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" -v "$PWD/spec:/usr/src/app/spec" specmatic/enterprise test
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 Specmatic-async will:
diff --git a/docs/supported_protocols/asyncapi/aws-sns.mdx b/docs/supported_protocols/asyncapi/aws-sns.mdx
@@ -212,7 +212,7 @@ Start your application that implements the AsyncAPI specification. The applicati
 Execute the contract tests using the Specmatic Docker image:
 
 ```bash
-docker run --network host -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" -v "$PWD/spec:/usr/src/app/spec" specmatic/enterprise test
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 Specmatic-async will:
diff --git a/docs/supported_protocols/asyncapi/aws-sqs.mdx b/docs/supported_protocols/asyncapi/aws-sqs.mdx
@@ -135,7 +135,7 @@ Start your application that implements the AsyncAPI specification. The applicati
 Execute the contract tests using the Specmatic Docker image:
 
 ```bash
-docker run --network host -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" -v "$PWD/spec:/usr/src/app/spec" specmatic/enterprise test
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 Specmatic-async will:
diff --git a/docs/supported_protocols/asyncapi/index.mdx b/docs/supported_protocols/asyncapi/index.mdx
@@ -37,11 +37,7 @@ To help you verify the above with a No-Code approach, Specmatic will send exampl
 Basic run:
 
 ```bash
-docker run --rm --network host \
-  -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-  -v "$PWD/spec:/usr/src/app/spec" \
-  -v "$PWD/build/reports/specmatic:/usr/src/app/build/reports/specmatic" \
-   specmatic/enterprise test
+docker run --rm --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 ### Key Capabilities
@@ -246,11 +242,7 @@ Replace values in angle brackets (`<...>`) with your actual configuration.
 Start your application with its dependencies (SQS, Kafka, etc.), then run:
 
 ```bash
-docker run --rm --network host \
-  -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-  -v "$PWD/spec:/usr/src/app/spec" \
-  -v "$PWD/build/reports/specmatic:/usr/src/app/build/reports/specmatic" \
-   specmatic/enterprise test
+docker run --rm --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 This generates and executes contract tests based on your AsyncAPI specification.
@@ -346,11 +338,7 @@ contracts:
 **Step 3: Start the Mock**
 
 ```bash
-docker run --rm --network host \
-  -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-  -v "$PWD/spec:/usr/src/app/spec" \
-  -v "$PWD/build/reports/specmatic:/usr/src/app/build/reports/specmatic" \
- specmatic/enterprise virtualize
+docker run --rm --network host -v "$(pwd):/usr/src/app" specmatic/enterprise mock
 ```
 
 **How It Works**:
@@ -370,7 +358,7 @@ For examples in `<SPEC_NAME>_examples/` directory:
 
 ```bash
 docker run --rm \
-  -v "$PWD/spec:/usr/src/app/spec" \
+  -v "$(pwd):/usr/src/app" \
   specmatic/enterprise examples validate \
   --spec-file spec/order-service.yaml
 ```
@@ -379,8 +367,7 @@ docker run --rm \
 
 ```bash
 docker run --rm \
-  -v "$PWD/spec:/usr/src/app/spec" \
-  -v "$PWD/custom-examples:/usr/src/app/custom-examples" \
+  -v "$(pwd):/usr/src/app" \
   specmatic/enterprise examples validate \
   --spec-file spec/order-service.yaml \
   --examples custom-examples
diff --git a/docs/supported_protocols/asyncapi/jms.mdx b/docs/supported_protocols/asyncapi/jms.mdx
@@ -310,7 +310,7 @@ Start your application that implements the AsyncAPI specification. The applicati
 Execute the contract tests using the Specmatic Docker image:
 
 ```bash
-docker run --network host -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" -v "$PWD/spec:/usr/src/app/spec" specmatic/enterprise test
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 Specmatic-async will:
diff --git a/docs/supported_protocols/asyncapi/kafka.mdx b/docs/supported_protocols/asyncapi/kafka.mdx
@@ -83,7 +83,7 @@ Please refer to [Specmatic documentation](/references/configuration) for more de
 Now we can run below command to spin a Kafka mock server. Please note the volume mapping to pass the specmatic.yaml to the Kafka Docker image and also the port mappings.
 
 ```shell
-docker run -p 9092:9092 -p 2181:2181 -p 29092:29092 -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" specmatic/enterprise
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise
 ```
 This should produce logs that shows that Specmatic Kafka server has started and listening on topics.
 
@@ -99,7 +99,7 @@ Starting api server on port:29092
 
 The API server can be started on a port other than 29092 by passing the desired port via `--mock-server-api-port` CLI argument as follows.
 ```shell
-docker run -p 9092:9092 -p 2181:2181 -p 3000:3000 -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" specmatic/enterprise --mock-server-api-port=3000
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise --mock-server-api-port=3000
 ```
 
 **Note:**
@@ -110,11 +110,7 @@ However, if you need to test against an **existing Kafka broker** (e.g., one run
 For example, to connect to a Kafka broker running on `localhost:9092`, use the following command:
 
 ```bash
-docker run -p 9999:9999 \
-  -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-  --network host \
-  specmatic/enterprise \
-  --external-broker-url localhost:9092
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise --external-broker-url localhost:9092
 ```
 
 The `--network host` flag is important when using `localhost` for the broker address, as it allows the container to access the host network directly. This avoids common issues with Docker container networking when referring to services on the host machine.
@@ -378,10 +374,10 @@ Start the Specmatic Kafka mock server using the following command:
 
 ```bash
 docker run --rm --name specmatic-kafka-mock \
-  -p 9999:9999 \
-  -v "$PWD/spec.yaml:/usr/src/app/spec.yaml" \
+  --network host \
+  -v "$(pwd):/usr/src/app" \
   specmatic/enterprise \
-  virtualize spec.yaml \
+  mock spec.yaml \
   --external-broker-url host.docker.internal:9092
 ```
 
@@ -495,7 +491,7 @@ To test this service from the command line, follow the below steps.
 2. **Run the Service**: Start your service locally.
 3. **Run Contract Tests**: Use the following command to run the contract tests against the service by replacing `kafka_broker_host` and `kafka_broker_port` with appropriate values:
 ```shell
-docker run --network="host" -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" specmatic/enterprise test --host=<kafka_broker_host> --port=<kafka_broker_port>
+docker run --network="host" -v "$(pwd):/usr/src/app" specmatic/enterprise test --host=<kafka_broker_host> --port=<kafka_broker_port>
 ```
 
 To get information around all the CLI args of the `test` command, run the following command.
@@ -568,7 +564,7 @@ Start your application that implements the AsyncAPI specification. The applicati
 Execute the contract tests using the Specmatic Docker image:
 
 ```bash
-docker run --network host -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" -v "$PWD/spec:/usr/src/app/spec" specmatic/enterprise test
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 Specmatic-async will:
diff --git a/docs/supported_protocols/asyncapi/migrate-from-specmatic-kafka-to-async.mdx b/docs/supported_protocols/asyncapi/migrate-from-specmatic-kafka-to-async.mdx
@@ -1,12 +1,12 @@
 ---
-title: Migrating to specmatic-async
+title: Migrating to Specmatic Enterprise
 sidebar_position: 11
-sidebar_label: Migrating to specmatic-async
+sidebar_label: Migrating to Specmatic Enterprise
 ---
 
-# Migrating from `specmatic-kafka` to `specmatic-async`
+# Migrating from `specmatic-kafka` to `specmatic enterprise`
 
-Migrating to `specmatic-async` unlocks multi-protocol support, improved configuration, and a unified approach to async contract testing and mocking. This guide walks you through the key steps for a smooth transition.
+Migrating to `specmatic enterprise` unlocks multi-protocol support, improved configuration, and a unified approach to async contract testing and mocking. This guide walks you through the key steps for a smooth transition.
 
 ## Migration Steps
 
@@ -46,7 +46,7 @@ contracts:
 Refer to the [Configuration Reference](./index.mdx#configuration-reference) for all available options.
 
 ### 2. Update Docker Image
-Replace the `specmatic-kafka` image with `specmatic-async` in your Docker commands.
+Replace the `specmatic/specmatic-kafka` image with `specmatic/enterprise` in your Docker commands.
 
 **Before:**
 ```bash
@@ -73,10 +73,9 @@ public class KafkaContractTest implements SpecmaticKafkaContractTest {
 ```
 **After:**
 ```java
-import com.specmatic.async.AsyncMock;
-import com.specmatic.async.SpecmaticAsyncContractTest;
+import io.specmatic.enterprise.SpecmaticContractTest
 
-public class AsyncContractTest implements SpecmaticAsyncContractTest {
+public class AsyncContractTest implements SpecmaticContractTest {
     // ...
 }
 ```
@@ -119,9 +118,9 @@ jobs:
       - name: Run Contract Tests
         run: |
           docker run --rm \
-            -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-            -v "$PWD/spec:/usr/src/app/spec" \
-            -v "$PWD/specmatic-kafka-config.properties:/usr/src/app/specmatic-kafka-config.properties" \
+            -v "$(pwd)/specmatic.yaml:/usr/src/app/specmatic.yaml" \
+            -v "$(pwd)/spec:/usr/src/app/spec" \
+            -v "$(pwd)/specmatic-kafka-config.properties:/usr/src/app/specmatic-kafka-config.properties" \
            specmatic/enterprise test
 ```
 
@@ -169,25 +168,25 @@ jobs:
       - name: Run Contract Tests
         run: |
           docker run --rm \
-            -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-            -v "$PWD/spec:/usr/src/app/spec" \
+            -v "$(pwd)/specmatic.yaml:/usr/src/app/specmatic.yaml" \
+            -v "$(pwd)/spec:/usr/src/app/spec" \
             specmatic/enterprise test
 ```
 
 ### Docker Setup Migration
 **Before (specmatic-kafka):**
 ```bash
 docker run --rm \
-  -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-  -v "$PWD/spec:/usr/src/app/spec" \
-  -v "$PWD/specmatic-kafka-config.properties:/usr/src/app/specmatic-kafka-config.properties" \
+  -v "$(pwd)/specmatic.yaml:/usr/src/app/specmatic.yaml" \
+  -v "$(pwd)/spec:/usr/src/app/spec" \
+  -v "$(pwd)/specmatic-kafka-config.properties:/usr/src/app/specmatic-kafka-config.properties" \
  specmatic/enterprise test
 ```
 **After (specmatic-async):**
 ```bash
 docker run --rm \
-  -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-  -v "$PWD/spec:/usr/src/app/spec" \
+  -v "$(pwd)/specmatic.yaml:/usr/src/app/specmatic.yaml" \
+  -v "$(pwd)/spec:/usr/src/app/spec" \
    specmatic/enterprise test
 ```
 
diff --git a/docs/supported_protocols/asyncapi/mqtt.mdx b/docs/supported_protocols/asyncapi/mqtt.mdx
@@ -115,7 +115,7 @@ Start your application that implements the AsyncAPI specification. The applicati
 Execute the contract tests using the Specmatic Docker image:
 
 ```bash
-docker run --network host -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" -v "$PWD/spec:/usr/src/app/spec" specmatic/enterprise test
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 Specmatic-async will:
diff --git a/docs/supported_protocols/asyncapi/rabbit-mq.mdx b/docs/supported_protocols/asyncapi/rabbit-mq.mdx
@@ -140,7 +140,7 @@ Start your application that implements the AsyncAPI specification. The applicati
 Execute the contract tests using the Specmatic Docker image:
 
 ```bash
-docker run --network host -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" -v "$PWD/spec:/usr/src/app/spec" specmatic/enterprise test
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise test
 ```
 
 Specmatic-async will:
diff --git a/docs/supported_protocols/graphql.mdx b/docs/supported_protocols/graphql.mdx
@@ -80,8 +80,7 @@ type Product {
 Run the following command to start the GraphQL stub:
 
 ```bash
-docker run -v "$PWD:/sandbox" -p 9000:9000 \
- specmatic/enterprise virtualize /sandbox/product-api.graphql
+docker run --network host -v "$(pwd):/sandbox" specmatic/enterprise mock /sandbox/product-api.graphql
 ```
 
 That's it! You now have a GraphQL stub server running on `localhost:9000/graphql` serving the schema defined in `product-api.graphql`.
@@ -156,8 +155,7 @@ response: [
 Run the following command to start the GraphQL stub:
 
 ```bash
-docker run -v "$PWD:/spec" -p 9000:9000 \
-  specmatic/enterprise virtualize /spec/product-api.graphql
+docker run --network host -v "$(pwd):/spec" specmatic/enterprise mock /spec/product-api.graphql
 ```
 
 **Step 3: Make a request to the stub server**
@@ -392,10 +390,7 @@ Here are some simple steps to try this out:
 
 **5.** Run the following command to start the GraphQL stub on `localhost:9000/graphql`:
    ```bash
-   docker run -v "$PWD/product-api.graphql:/usr/src/app/product-api.graphql" \
-     -v "$PWD/examples:/usr/src/app/examples" \
-     -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-      -p 9000:9000 specmatic/enterprise virtualize --port=9000 --examples=examples
+   docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise mock --port=9000 --examples=examples
    ```
 
 **6.** Make a request to query all the sub-selected fields specified in the example. You will get the exact response specified in the example. Use the following `curl` command to make this request:
@@ -551,10 +546,7 @@ To showcase this, let's reuse the folder structure established in the previous s
 
 4. **Run the GraphQL Stub**:
    ```bash
-   docker run -v "$PWD/product-api.graphql:/usr/src/app/product-api.graphql" \
-     -v "$PWD/examples:/usr/src/app/examples" \
-     -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-      -p 9000:9000 specmatic/enterprise virtualize --port=9000 --examples=examples
+   docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise mock --port=9000 --examples=examples
    ```
 
 5. **Send a Multi-Query Request**:
@@ -700,10 +692,7 @@ Let's see how it works using the same product-related GraphQL spec and example f
 
 4. **Run the GraphQL Stub**:
    ```bash
-   docker run -v "$PWD/product-api.graphql:/usr/src/app/product-api.graphql" \
-     -v "$PWD/examples:/usr/src/app/examples" \
-     -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" \
-      -p 9000:9000 specmatic/enterprise virtualize --port=9000 --examples=examples
+   docker run -v "$(pwd):/usr/src/app" specmatic/enterprise mock --port=9000 --examples=examples
    ```
 
 5. **Send a Multi-Field Request Using Aliases**:
diff --git a/docs/supported_protocols/grpc.mdx b/docs/supported_protocols/grpc.mdx
@@ -246,7 +246,7 @@ Also, the Specmatic gRPC Docker image, by nature, is completely language and tec
 To start the stub/service virtualization service, use the following command:
 
 ```bash
-docker run -p 9000:9000 -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" specmatic/enterprise virtualize
+docker run --network host -v "$(pwd):/usr/src/app" specmatic/enterprise mock
 ```
 
 This command mounts your local `specmatic.yaml` file into the container and exposes the stub service on port 9000. And uses the proto files listed under `consumes` section for starting up a service virtualization server.
@@ -269,7 +269,7 @@ contracts:
 To run tests against your BFF (Backend for Frontend), use this command:
 
 ```bash
-docker run --network host -v "$PWD/specmatic.yaml:/usr/src/app/specmatic.yaml" -v "$(pwd)/build/reports/specmatic:/usr/src/app/build/reports/specmatic" -e SPECMATIC_GENERATIVE_TESTS=true specmatic/enterprise test --port=8080 --host=host.docker.internal
+docker run --network host -v "$(pwd):/usr/src/app" -e SPECMATIC_GENERATIVE_TESTS=true specmatic/enterprise test --port=8080 --host=host.docker.internal
 ```
 
 This command mounts your `specmatic.yaml` file and runs tests against a service running on port 8080 by generating gRPC requests based on the profiles listed under `provides` section.
