Post docker compose and starting the microservice , service url comes back ERR_EMPTY_RESPONSE

[soumya-ghosh-sndk]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

The service is already running as shown in the following snapshot :

**But when I test the url in the browser as shown below

http://localhost:63781/ there is no response.** Please see below.

Final API url : http://localhost:63781/api/Product

Build output

1>docker-compose -f "C:\Microservice\ProductMicroService\docker-compose.yml" -f "C:\Microservice\ProductMicroService\docker-compose.override.yml" -f "C:\Microservice\ProductMicroService\obj\Docker\docker-compose.vs.debug.g.yml" -p dockercompose12200649739767505237 --ansi never up -d
1> Container ProductMicroService Running
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Build started at 6:54 PM and took 03.530 seconds ==========

Container tools output -

========== Launching ==========
========== Debugging ==========
========== Debugging ==========
========== Launching ==========
========== Launching ==========
========== Launching ==========
========== Launching ==========
========== Launching ==========
========== Launching ==========
========== Debugging ==========

IDE used: Visual Studio 2022 Professional

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

7.0.304

Anything else?

No response

[mitchdenny]

Which template did you use in Visual Studio?

[soumya-ghosh-sndk]

I have used ASP.NET Core WebAPI .Please note when I run via IISExpress with Swagger there is no issue.

This url is accessible :

http://localhost:51530/swagger/index.html

[soumya-ghosh-sndk]

Any update ?

[mitchdenny]

I was not able to reproduce this issue. I suspect there might be something environmental on your machine causing this. Couple of things to try to debug the issue. Try doing a curl of the endpoint from your terminal. If that fails. See if the endpoint is listening inside the container. Exec into the running container and see what processes are running and if they are responsive:

docker exec -it [container id] /bin/sh
$ apt-get update -y
$ apt-get install -y wget
$ wget --no-check-certificate https://localhost/weatherforecast # I'm just using the template API surface in this example

[soumya-ghosh-sndk]

Thanks for those commands.I executed those as suggested but this is what I get:

C:\Microservice\ProductMicroService>docker exec -it b4ab5bd0fb6c /bin/sh

apt-get update -y

Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 Packages [8183 kB]
Get:5 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [252 kB]
Get:6 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [14.8 kB]
Fetched 8658 kB in 3s (2511 kB/s)
Reading package lists... Done

apt-get install -y wget

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libpsl5 publicsuffix
The following NEW packages will be installed:
libpsl5 publicsuffix wget
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 1149 kB of archives.
After this operation, 4001 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 libpsl5 amd64 0.21.0-1.2 [57.3 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 wget amd64 1.21-1+deb11u1 [964 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 publicsuffix all 20220811.1734-0+deb11u1 [127 kB]
Fetched 1149 kB in 1s (2211 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libpsl5:amd64.
(Reading database ... 6988 files and directories currently installed.)
Preparing to unpack .../libpsl5_0.21.0-1.2_amd64.deb ...
Unpacking libpsl5:amd64 (0.21.0-1.2) ...
Selecting previously unselected package wget.
Preparing to unpack .../wget_1.21-1+deb11u1_amd64.deb ...
Unpacking wget (1.21-1+deb11u1) ...
Selecting previously unselected package publicsuffix.
Preparing to unpack .../publicsuffix_20220811.1734-0+deb11u1_all.deb ...
Unpacking publicsuffix (20220811.1734-0+deb11u1) ...
Setting up libpsl5:amd64 (0.21.0-1.2) ...
Setting up wget (1.21-1+deb11u1) ...
Setting up publicsuffix (20220811.1734-0+deb11u1) ...
Processing triggers for libc-bin (2.31-13+deb11u6) ...

wget --no-check-certificate http://localhost:64404/api/Product

--2023-07-05 05:26:08-- http://localhost:64404/api/Product
Resolving localhost (localhost)... 127.0.0.1, ::1
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:26:09-- (try: 2) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:26:11-- (try: 3) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:26:14-- (try: 4) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:26:18-- (try: 5) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:26:23-- (try: 6) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:26:29-- (try: 7) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:26:36-- (try: 8) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:26:44-- (try: 9) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:26:53-- (try:10) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:27:03-- (try:11) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:27:13-- (try:12) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:27:23-- (try:13) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

--2023-07-05 05:27:33-- (try:14) http://localhost:64404/api/Product
Connecting to localhost (localhost)|127.0.0.1|:64404... failed: Connection refused.
Connecting to localhost (localhost)|::1|:64404... failed: Cannot assign requested address.
Retrying.

[mitchdenny]

Using wget again, use port 80 (or 443 if you have HTTPS configured). Inside the container, the app is running on port 80 from what I can tell from your docker ps screenshot above.

[soumya-ghosh-sndk]

I get the same error, please see below -

# wget --no-check-certificate http://localhost:80/api/Product
--2023-07-05 06:06:53-- http://localhost/api/Product
Resolving localhost (localhost)... 127.0.0.1, ::1
Connecting to localhost (localhost)|127.0.0.1|:80... failed: Connection refused.
Connecting to localhost (localhost)|::1|:80... failed: Cannot assign requested address.
Retrying.

--2023-07-05 06:06:54-- (try: 2) http://localhost/api/Product
Connecting to localhost (localhost)|127.0.0.1|:80... failed: Connection refused.
Connecting to localhost (localhost)|::1|:80... failed: Cannot assign requested address.
Retrying.

--2023-07-05 06:06:56-- (try: 3) http://localhost/api/Product
Connecting to localhost (localhost)|127.0.0.1|:80... failed: Connection refused.
Connecting to localhost (localhost)|::1|:80... failed: Cannot assign requested address.
Retrying.

--2023-07-05 06:06:59-- (try: 4) http://localhost/api/Product
Connecting to localhost (localhost)|127.0.0.1|:80... failed: Connection refused.
Connecting to localhost (localhost)|::1|:80... failed: Cannot assign requested address.
Retrying.

[soumya-ghosh-sndk]

Any update ?

[soumya-ghosh-sndk]

Any update ? Awaiting inputs.

[soumya-ghosh-sndk]

One observation using curl -
Invoking service url using docker container:

C:\Microservice\ProductMicroService>curl -v -L http://localhost:51594/ProductMicroService/api/Product

• Trying 127.0.0.1:51594...
• Connected to localhost (127.0.0.1) port 51594 (#0) Connection is established.

GET /ProductMicroService/api/Product HTTP/1.1
Host: localhost:51594
User-Agent: curl/8.0.1
Accept: /

• Empty reply from server
• Closing connection 0
  curl: (52) Empty reply from server

---

Invoking service url using IIS Express
C:\Microservice\ProductMicroService>curl -v -L http://localhost:51530/api/Product

• Trying 127.0.0.1:51530...
• Connected to localhost (127.0.0.1) port 51530 (#0)

GET /api/Product HTTP/1.1
Host: localhost:51530
User-Agent: curl/8.0.1
Accept: /

< HTTP/1.1 200 OK
< Transfer-Encoding: chunked
< Content-Type: application/json; charset=utf-8
< Server: Microsoft-IIS/10.0
< X-Powered-By: ASP.NET
< Date: Thu, 06 Jul 2023 09:10:20 GMT
<
[{"id":1,"name":"Note5","description":"Samsung Mobile Phone-5","price":45000.00,"categoryId":1}]* Connection #0 to host localhost left intact

In the second method it returns the expected .json output

[mitchdenny]

Those URLs are different?

Nevermind ;)

[mitchdenny]

Can you put together a simple repro and post it in a public GitHub repro. I want to make sure I'm reproducing using the same setup that you are.

[soumya-ghosh-sndk]

Yes.The docker url needs to be prefixed with the name of the container.

Please find below the snapshot taken from DockerDesktop

[soumya-ghosh-sndk]

I have already mentioned all the details.
Basically the API responds locally via IISExpress but does not with local docker container. Visual Studio 2022 Professional is used for development using ASP.NET Core Web API