Hello I ve got a bit of an issue deploying wiremock as an ap WireMock #help

Hello, I've got a bit of an issue deploying wiremo...

Patrick Davy

05/01/2025, 4:27 PM

Hello, I've got a bit of an issue deploying wiremock as an appservice in azure... We're using wiremock to act as a stub for a training mode in our app. The plan was to build our own image with the json config baked in, that works fine locally. It also works fine when I build/push to our azure container registry from our pipelines and pull locally. Now when it comes to deploying into an azure app service, the server responds but all of our mapping config isn't in the

home/wiremock

directory anymore, it's exactly the same image as the one I pulled and tested locally. Any ideas what's going on here or potential avenues of investigation?

Patrick Davy

05/02/2025, 9:36 AM

After coming back to this with fresh eyes, I figured out a workaround. One of the many images that wasn't working below.

Copy code

FROM wiremock/wiremock:3.12.1-1

WORKDIR /home/wiremock
COPY ./Configuration/mappings ./mappings
COPY ./Configuration/__files ./__files

RUN ["ls", "mappings"]
RUN ["ls", "__files"]

ENTRYPOINT ["/docker-entrypoint.sh", "--global-response-templating", "--disable-gzip", "--verbose"]

It turns out

/home

is a special directory for runtime use in app services that acts as persistent storage. If I changed to a different directory and configured wiremock to use that, it magically works. e.g.

Copy code

FROM wiremock/wiremock:3.12.1-1

WORKDIR /wiremock/configuration
COPY ./Configuration/mappings ./mappings
COPY ./Configuration/__files ./__files

RUN ["ls", "mappings"]
RUN ["ls", "__files"]

ENTRYPOINT ["/docker-entrypoint.sh", "--global-response-templating", "--disable-gzip", "--verbose", "--root-dir=/wiremock/configuration"]

2 Views

Open in Slack

Previous Next