This is a question of docker configuration and minor code changes.

If not, you may use the CarApi and CarClient projects (see below) to implement your own solution.

When this is done, you need to add a docker-compose project to your solution.

Docker networking, as well as kubernetes handles all this magic.

Instead of localhost, the name of the service, as defined in the docker-compose, is used.

To call the CarApi, use You dont need to set the port number as the port number is an external attribute.

This variable is defined in the docker-compose.yml file like this.

We must expose port 54411 by changing the docker configuration file for CarApi like this.

You can now run your containerized solution in Visual Studio.

Run the docker-compose project with F5 to ensure the images are updated.

In PowerShell, cd to the solution folder where docker-compose.yml is located.

Then run the docker-compose command like this.

It manually maps the empty container to the filesystem to make possible debugging, Edit and Continue features and so on.

Build the image in the Release configuration to make it usable.

The query I have is - have you been able to access the api from a remote machine I have enabled the ports through the firewall as well but the Ip address of the container itself is still not accessible from a remote machine.

In my experience creating docker builds to run.NET Core WEB applications on IIS takes much more effort.

Docker For Mac Api Url