I really want to move onto other features of the product but I am stuck on this. Port 80 is determined per the documentation from export INGRESS_PORT=$(kubectl -n istio-system get service istio- ingressgateway -o have followed the Istio documents to a tee, but cannot access the service from the outside via browser or curl no matter what I try. It does not say connection refused so it seems the port is open. (I dont see any option on Docker Edge to open port 80 before starting Kubernetes) Not sure what the issue is. I assigned this as the host per the documents. As per the documents I first checked if there was a load balancer in place and saw localhost was the IP address. But I have not been able to access it externally at all. The booklist app deploys perfectly and I have confirmed the service is responding. I am running Kubernetes from Docker for Mac (Edge release). Engineer evaluating Istio for a use on our project. I think it would be great if people could run Istio from Mac Docker Edge and hope I can get some help on this for anyone who wants to do this. Everything is accessible internally but when I try to access the service externally I get no server response. I am just trying to run the demo bookinfo app that ships with Kubernetes. Now, it will listen to all network interfaces on the local machine at port 5000, which is exactly what I want.Fyi, Docker Edge is just Docker for Mac app with integrated Kubernetes. UseContentRoot(Directory.GetCurrentDirectory()) So to fix it, I can tell Kestrel to listen using the UseUrls() method and specify interfaces to listen on: public static void Main(string args) Sort of a bonehead moment on my part but there you are. That doesn’t allow it to be viewed externally from the host. I found out that by default, ASP.NET Core applications only listen on the loopback interface - that’s why it showed me localhost:5000. The syntax for docker -p is HOST:CONTAINER, and I’ve made them 5000 on both sides just for testing, but I’m still not getting a response. It’s listening on localhost (the docker container), and I’ve exposed port 5000, right? Maybe my port settings are wrong when I spin up the container? Let’s check: docker run -i -p 5000:5000 -name my-project -t my-project:latest Docker was set up correctly and ASP.NET Core applications listen on port 5000 typically:Ĭomplete Dockerfile: FROM microsoft/dotnet:1.1.0-runtimeĪRG source=./src/bin/Release/netcoreapp1.1/publishĪSP.NET Core dotnet run output: my-project We use Docker’s Network feature to create a virtual network for our docker containers but for some reason I wasn’t able to issue a curl request against the ASP.NET Docker container, it simply returned: When attempting to Dockerize my ASP.NET Core micro-service, I ran into an interesting issue.
0 kommentar(er)
