HTTP call to Logic App in a Docker Container

Question

I've followed getting started with Logic Apps in a Container, in Azure Tips & Tricks #311, which worked OK. I also consulted Vinnie James, which is similar

The Logic App runs on receipt of a HTTP request, which - inside VS Code - is localhost, easily used from a browser

But when I go to the next step, to build an image and run it in Docker, I'm not at all clear how to to make a similar HTTP request; Docker is running on the same W10 machine, using WSL-2

Dockerfile (corrected):

FROM mcr.microsoft.com/azure-functions/dotnet:3.0.14492-appservice
ENV AzureWebJobsStorage=DefaultEndpointsProtocol=https;AccountName=XXX;AccountKey=XXX;EndpointSuffix=core.windows.net
ENV AzureWebJobsScriptRoot=/home/site/wwwroot \
    AzureFunctionsJobHost__Logging__Console__IsEnabled=true \
    FUNCTIONS_V2_COMPATIBILITY_MODE=true
ENV WEBSITE_HOSTNAME localhost
ENV WEBSITE_SITE_NAME testqueue1
ENV AZURE_FUNCTIONS_ENVIRONMENT Development
COPY . /home/site/wwwroot

Attempted Docker run: docker run -p 80:7071 image1

Response is HTTP request sent, awaiting response... No data received

This despite (very simple) Logic App issuing a 200 response immediately after trigger; looks like App is not initiated ...

Answer 1

First of all and regarding the answer in the comments: please just add the contents of the Dockerfile and the run command to the question, otherwise they're difficult to read.

---

Taking into account that you have the following Dockerfile:

FROM mcr.microsoft.com/azure-functions/node:3.0

ENV AzureWebJobsStorage DefaultEndpointsProtocol=https;AccountName=XXX;AccountKey=XXX;EndpointSuffix=core.windows.net 
ENV AzureWebJobsScriptRoot=/home/site/wwwroot \
    AzureFunctionsJobHost__Logging__Console__IsEnabled=true \
    FUNCTIONS_V2_COMPATIBILITY_MODE=true 
ENV WEBSITE_HOSTNAME localhost 
ENV WEBSITE_SITE_NAME test1 
ENV AZURE_FUNCTIONS_ENVIRONMENT Development 

COPY . /home/site/wwwroot 

and that you're running it with docker run -p 5000 image1

The main thing that I see here is that you're only indicating the containerPort but not the hostPort, so you're exposing a random port in the host.

If you do docker ps, you'll be able to see the port that you're forwarding. For example let's say that I have my image busybox and that I run it with docker run -it --rm -p 5000 busybox.

❯ docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED         STATUS         PORTS                     NAMES
05927642abfc   busybox   "sh"      6 seconds ago   Up 5 seconds   0.0.0.0:51883->5000/tcp   elated_gauss

As you can see, I'd have to access to the port 51883 in localhost to access to the port 5000 in the container.

On the other hand, if I run my container with: docker run -it --rm -p 5000:5000 busybox

❯ docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED        STATUS        PORTS                    NAMES
c0aab9646d1a   busybox   "sh"      1 second ago   Up 1 second   0.0.0.0:5000->5000/tcp   busy_roentgen

Now I can access to the port 5000 of the container referring to the port 5000 on localhost.