:wave: Hello, team! I am having wiremock as a dock...
# wiremock-javav
vivid973
09/19/2025, 8:45 PM👋 Hello, team! I am having wiremock as a docker container. I have been struggling to add grpc extension to it in a docker-compose file so that I can use the grpc mock. My local folders are in the same folder of the docker-compose.yml file. I keep getting different error from Java. Could you guide me how to do this? Should I use standalone jar? Many thanks.
wiremock:
image: wiremock/wiremock:3.13.1-1
ports:
- "9090:8080" # gRPC port
volumes:
- ./mappings:/home/wiremock/mappings
- ./proto-descriptors:/home/wiremock/grpc
- ./extensions/wiremock-grpc-extension-0.11.0.jar:/var/wiremock/extensions/wiremock-grpc-extension-0.11.0.jar
command: [
"--port", "8080",
"--verbose",
"--root-dir",
"/home/wiremock",
"--extensions",
"org.wiremock.grpc.GrpcExtensionFactory"
]
l
Lee Turner
09/22/2025, 11:32 AMHi, yes, I think you need to use the standalone grpc extension. Also, I think you shouldn't need to use the
"--extensions", "org.wiremock.grpc.GrpcExtensionFactory"Lee Turner
09/22/2025, 11:32 AMI think I put an example of this together locally. Let me see if I can upload it to github for you to reference
Lee Turner
09/22/2025, 11:42 AMI have just pushed this repo for you to take a look at - https://github.com/leeturner/wiremock-standalone-grpc-example
Lee Turner
09/22/2025, 11:42 AMHopefully that is all pretty self explanatory but if not let me know
v
vivid973
09/22/2025, 2:08 PMMany thanks, Lee. I will take try and let you know.
vivid973
09/22/2025, 2:46 PMHello Lee, appreciate your help on this. If I have docker compose defined with . in front of all volumes. I got below error.
* Executing task: docker logs --tail 1000 -f a422ad01b1c7386e0c9cff0792924afdbf3948f53fb06fb1266cb7760fc8b8fb
2025-09-22 142847.725 Verbose logging enabled
Exception in thread "main" com.github.tomakehurst.wiremock.standalone.MappingFileException: Error loading file /home/wiremock/./mappings/hello-grpc.json:
Unrecognized field "grpc" (class com.github.tomakehurst.wiremock.matching.RequestPattern), not marked as ignorable
at com.github.tomakehurst.wiremock.standalone.JsonFileMappingsSource.loadMappingsInto(JsonFileMappingsSource.java:126)
at com.github.tomakehurst.wiremock.core.WireMockApp.loadMappingsUsing(WireMockApp.java:288)
at com.github.tomakehurst.wiremock.core.WireMockApp.loadDefaultMappings(WireMockApp.java:282)
at com.github.tomakehurst.wiremock.core.WireMockApp.<init>(WireMockApp.java:143)
at com.github.tomakehurst.wiremock.WireMockServer.<init>(WireMockServer.java:68)
at com.github.tomakehurst.wiremock.standalone.WireMockServerRunner.run(WireMockServerRunner.java:71)
at wiremock.Run.main(Run.java:23)
* Terminal will be reused by tasks, press any key to close it.
If I remove the . in front of all volumes, it seems to work from my test script calling the mocked service. However, the wiremock container logs seems to be missing the grpc extension but have only default response-template and webhook. Is this a bug?
version: 3.13.1
port: 8080
enable-browser-proxying: false
disable-banner: false
no-request-journal: false
verbose: true
extensions: response-template,webhook
2025-09-22 144045.866 Admin request received:
[0000000:1] - GET /health
Host: [localhost:8080]
User-Agent: [curl/8.5.0]
Accept: [/]
l
Lee Turner
09/22/2025, 2:51 PMHi, are you saying that you need the
. Copy code
version: 3.13.1
port: 8080
enable-browser-proxying: false
disable-banner: false
no-request-journal: false
verbose: true
extensions: grpc-client-factory,grpc-stub-transformer,grpc,response-template,webhookv
vivid973
09/22/2025, 2:55 PMHi Lee, if I put docker compose like below without . for all volumes container can start normally without error, but the extension was not loaded in the log. And I confirm I was testing a normal http mock rather than the grpc service. Sorry for the basics and confusion.
wiremock:
image: wiremock/wiremock:3.13.1-1-alpine
ports:
- "9090:8080" # gRPC port
volumes:
- /mappings:/home/wiremock/mappings
- /proto-descriptors:/home/wiremock/grpc
- /extensions:/var/wiremock/extensions
entrypoint: [ "/docker-entrypoint.sh", "--verbose" ]
l
Lee Turner
09/22/2025, 3:01 PMIt is difficult to say what the issue is without seeing all the files you have in the different locations. Could you put a simple project together somewhere that reproduces the issue (GitHub maybe) so I can take a look ?
Also, it looks like you are assuming wiremock runs on port 9090 but you are not telling wiremock to start on that port.
v
vivid973
09/22/2025, 3:03 PMOK, I will try from my side and share with you. I am missing a lot of basics and work with gpt. Thanks for your patience.
l
Lee Turner
09/22/2025, 3:09 PMMaybe it would be worth pulling down the example I uploaded and using that as your base. As far as I know that all loads correctly etc
🙌 1
v
vivid973
09/22/2025, 3:38 PMHi Lee. Yes, your example works perfectly on my local. I can see grpc extension in log and also container started without issue. I am not able to reproduce what was wrong from my side. I will try the test script and see if the grpc mock is working. Thank you very much.
👍 1
vivid973
09/22/2025, 3:42 PMGRPC test works perfectly. Again, many thanks for your help. This example is very useful. GPT was making too much stories.
l
Lee Turner
09/22/2025, 3:43 PMNo problem at all. Glad you are up and running.
v
vivid973
09/22/2025, 4:14 PMHi @Lee Turner , I was using below 2 methods to change response in my web server mock test with wiremock if needed. Is it the same for gRPC mock?
response = requests.post(f"{self._base_url}/__admin/mappings", json=mapping)
bulk_payload = {"mappings": list(self._mappings.values())}
response = requests.post(f"{self._base_url}/__admin/mappings/import", json=bulk_payload)
l
Lee Turner
09/22/2025, 4:17 PMYes, you can use the mappings endpoints to change the stubs just the same. You need to remember that your responses still need to conform to the structure of the proto messages otherwise an exception will be thrown
👍 1
v
vivid973
09/25/2025, 4:53 AMHello, Lee. I am mocking my real gRPC server. I found the .dsc home/wiremock/grpc folder is not making effect if I am calling gRPC using requests.post the same way as your example. As long as my requests.post matches mappings.json, wiremock will respond, even if I have the wrong .dsc file mounted to home/wiremock/grpc. Then what is the function of .dsc file in wiremock grpc extnesion? If I am initiating a real gRPC call from my test code like below, I will receive "Code: Unimplemented
Message: No matching stub mapping found for gRPC request", even though I have the .dsc file generated from proto file monted to homt/wiremock/grpc. Could you help explain?
async def query_channel_metadata(
job_name: str, run_number: int, pass_code: str
) -> _schema.ReadMetadataResponse:
request = _schema.ReadMetadataRequest()
if job_name is not None:
request.job_name = job_name
if run_number is not None:
request.run_number = run_number
if pass_code is not None:
request.pass_code = pass_code
proto_req = _grpc_helpers.dataclass_to_protobuff(
request, MaxwellChannel_pb2.ReadMetadataRequest()
)
channel = grpc.aio.insecure_channel("localhost:9090")
_stub_factory = MaxwellChannel_pb2_grpc.MaxwellChannelStub
stub = _stub_factory(channel)
metadata = (
("client-id", "9OtCVlEODHMYKUYsrpk6"),
)
response_coro = stub.QueryChannelMetadata(
request=proto_req, metadata=metadata
)
response = await response_coro
log_request(
await get_tracking_id_from_coro(response_coro), "QueryChannelMetadata"
)
return response
async def test_query_channel_metadata():
await query_channel_metadata(
job_name="Job3", run_number=1, pass_code="log"
)
l
Lee Turner
10/02/2025, 3:46 PMSorry, I am not sure I fully understand your issue. Could you explain the flow of what you are doing and what you are expecting to work and what isn't ?
78 Views